CodeSampleX

Recordsgolanggolang.org/x/netv0.17.0

Change the conditions
Fixed
OSalpine musl Package versionv0.17.0 Symbolwhole package
Filter Runtimego 1.26 Architecturex64 Package managergo Execution contextgo libcmusl Clear filters

Current conditions

golang.org/x/net @v0.17.0alpine musl · x64 · go 1.26 · go · go

package-level total, not an API

1 of 1 passed

Verified — this network ran a contract at this coordinate.

there is a sample here, and our run of it at this coordinate came back clean (5)

Project observations
2 / 2
Contract verifications
1 / 1
Usage records
1
Independent reporting peers
1
Last recorded
2026-09-05

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 5 · Steady 0

First observed break

v0.17.0

linux

31 FAIL · stage: UNKNOWN · fingerprint: sha256:9be950af9140edade9f2c5aa029896fb7dd194960195369ee277ef42a11d6868

Library Version Health Measured there Projects
golang.org/x/crypto v0.14.0 CANDIDATE Correlated change; unproven combination nothing measured 6 project-days
golang.org/x/sys v0.13.0 CANDIDATE Correlated change; unproven combination nothing measured 4 project-days
golang.org/x/sys v0.14.0 CANDIDATE Correlated change; unproven combination contract passed 2 project-days
golang.org/x/term v0.13.0 CANDIDATE Correlated change; unproven combination nothing measured 6 project-days
golang.org/x/text v0.13.0 CANDIDATE Correlated change; unproven combination builds observed 6 project-days

The measured column is about each dependency's own release, not about the pair. A resolver placing two releases side by side is not evidence that they work together.

Dependency versions across releases

What each release of this package resolved its children to. A child whose version moved is listed first: that is where an upgrade changed something underneath you.

Libraryv0.58.0v0.57.0v0.56.0v0.55.0v0.53.0v0.52.0v0.51.0v0.50.0v0.38.0v0.37.0v0.35.0v0.34.0v0.31.0v0.29.0v0.28.0v0.24.0v0.23.0v0.21.0v0.17.0v0.12.0v0.10.0v0.4.0v0.2.0v0.0.0-20210525063256-abc453219eb5v0.0.0-20210226172049-e18ecbb05110v0.0.0-20200625001655-4c5254603344v0.0.0-20190620200207-3b0461eec859v0.0.0-20190404232315-eb5bcb51f2a3v0.0.0-20190313220215-9f648a60d977
golang.org/x/crypto v0.55.0 v0.54.0 v0.54.0 v0.52.0 v0.50.0 v0.49.0 v0.48.0 v0.48.0 v0.36.0 v0.33.0 v0.32.0 v0.29.0 v0.27.0 v0.26.0 v0.22.0 v0.21.0 v0.20.0 v0.14.0 v0.11.0 v0.0.0-20200622213623-75b288015ac9 v0.0.0-20191011191535-87dc89f01550 v0.0.0-20200622213623-75b288015ac9 v0.0.0-20190313024323-a1f597ede03a
golang.org/x/sys v0.47.0 v0.47.0 v0.47.0 v0.45.0 v0.44.0 v0.42.0 v0.41.0 v0.41.0 v0.31.0 v0.31.0 v0.30.0 v0.29.0 v0.27.0 v0.25.0 v0.24.0 v0.19.0 v0.18.0 v0.17.0 v0.14.0 v0.10.0 v0.17.0 v0.47.0 v0.2.0 v0.47.0 v0.0.0-20210615035016-665e8c7367d1 v0.0.0-20200625212154-ddb9806d33ae v0.0.0-20190412213103-97732733099d
golang.org/x/term v0.45.0 v0.45.0 v0.45.0 v0.43.0 v0.42.0 v0.41.0 v0.40.0 v0.40.0 v0.30.0 v0.29.0 v0.28.0 v0.26.0 v0.24.0 v0.23.0 v0.19.0 v0.18.0 v0.17.0 v0.13.0 v0.10.0 v0.17.0 v0.2.0 v0.0.0-20201126162022-7de9c90e9dd1 v0.0.0-20201126162022-7de9c90e9dd1
golang.org/x/text v0.41.0 v0.40.0 v0.40.0 v0.37.0 v0.36.0 v0.35.0 v0.34.0 v0.34.0 v0.23.0 v0.23.0 v0.22.0 v0.21.0 v0.20.0 v0.18.0 v0.17.0 v0.14.0 v0.14.0 v0.14.0 v0.13.0 v0.11.0 v0.14.0 v0.5.0 v0.4.0 v0.3.6 v0.41.0 v0.3.0 v0.3.0 v0.3.0 v0.3.1-0.20180807135948-17ff2d5776d2

Moved: 4 · unchanged at every release: 0

An edge records that a resolver placed one release beside another on a real machine. It is not a claim that the two work together; that question is answered by samples and contracts, not by presence here.

Recent failure clusters