CodeSampleX

Recordsgolanggolang.org/x/netv0.55.0

Change the conditions
Fixed
OSwindows 11 Runtimego 1.26
Filter Package versionv0.55.0 Symbolwhole package Architecturex64 Package managergo 1 Clear filters

Current conditions

golang.org/x/net @v0.55.0windows 11 · x64 · go 1.26 · go 1

package-level total, not an API

11 of 13 passed

Observed — real project builds reported from this coordinate.

there is a sample here, and nothing of ours has run it at this coordinate yet (1)

Project observations
11 / 13
Contract verifications
nothing at this coordinate
Independent reporting peers
1
Failures with a captured fingerprint
0 / 2
Last recorded
2026-08-18
Evidence you can open

Dependencies

LibraryVersionMeasured thereProjects
golang.org/x/crypto v0.52.0 contract passed 2 project-days
golang.org/x/sys v0.45.0 contract passed 2 project-days
golang.org/x/term v0.43.0 contract passed 2 project-days
golang.org/x/text v0.37.0 contract passed 2 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.55.0v0.17.0
golang.org/x/crypto v0.52.0 v0.14.0
golang.org/x/sys v0.45.0 v0.13.0
golang.org/x/term v0.43.0 v0.13.0
golang.org/x/text v0.37.0 v0.13.0

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