Recordsgolanggolang.org/x/netv0.0.0-20190620200207-3b0461eec859
Change the conditions
Current conditions
golang.org/x/net @v0.0.0-20190620200207-3b0461eec859debian 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.
there is a sample here, and nothing of ours has run it at this coordinate yet (1)
- 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
Dependency changes observed: 3. No failure evidence is linked to these resolved trees yet.
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| golang.org/x/crypto | v0.0.0-20191011191535-87dc89f01550 | CHANGED Version changed, no linked failure | builds observed | 2 project-days |
| golang.org/x/sys | v0.0.0-20190412213103-97732733099d | CHANGED Version changed, no linked failure | nothing measured | 2 project-days |
| golang.org/x/text | v0.3.0 | CHANGED Version changed, no linked failure | nothing measured | 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.
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.