CodeSampleX

Recordsgolanggolang.org/x/netv0.0.0-20210226172049-e18ecbb05110

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

Current conditions

golang.org/x/net @v0.0.0-20210226172049-e18ecbb05110debian 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-04

Dependency Health

Observed combinations and failure evidence for this release

Changed 3 · Steady 0

Dependency changes observed: 3. No failure evidence is linked to these resolved trees yet.

Library Version Health Measured there Projects
golang.org/x/sys v0.0.0-20201119102817-f84b799fce68 CHANGED Version changed, no linked failure contract passed 4 project-days
golang.org/x/term v0.0.0-20201126162022-7de9c90e9dd1 CHANGED Version changed, no linked failure builds observed 4 project-days
golang.org/x/text v0.3.3 CHANGED Version changed, no linked failure builds observed 4 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.

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.