CodeSampleX

Recordsgolanggolang.org/x/netv0.4.0

Change the conditions
Fixed
Package versionv0.4.0
Filter OSdebian glibc Runtimego 1.26 Symbolwhole package Architecturex64 Package managergo Execution contextgo libcglibc Clear filters

Current conditions

golang.org/x/net @v0.4.0debian glibc · x64 · go 1.26 · go · go

package-level total, not an API

Recorded as present in projects. Nothing was run at this coordinate.

Observed — real project builds reported from this coordinate.

no sample at this coordinate yet

Project observations
nothing at this coordinate
Contract verifications
nothing at this coordinate
Usage records
1
Independent reporting peers
1
Last recorded
2026-09-01

Dependencies

LibraryVersionMeasured thereProjects
golang.org/x/sys v0.47.0 contract passed 1 project-day
golang.org/x/text v0.5.0 builds observed 1 project-day

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.53.0v0.52.0v0.17.0v0.4.0v0.0.0-20210525063256-abc453219eb5
golang.org/x/crypto v0.52.0 v0.50.0 v0.49.0 v0.14.0
golang.org/x/sys v0.45.0 v0.44.0 v0.42.0 v0.13.0 v0.47.0 v0.0.0-20220114195835-da31bd327af9
golang.org/x/term v0.43.0 v0.42.0 v0.41.0 v0.13.0
golang.org/x/text v0.37.0 v0.36.0 v0.35.0 v0.13.0 v0.5.0 v0.3.6

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.