Recordsgolanggolang.org/x/netv0.21.0
Change the conditions
Current conditions
golang.org/x/net @v0.21.0ubuntu glibc · x64 · go 1.26 · go 1
package-level total, not an API
2 of 4 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
- 2 / 4
- Contract verifications
- nothing at this coordinate
- Independent reporting peers
- 1
- Failures with a captured fingerprint
- 0 / 2
- Last recorded
- 2026-08-26
Dependency Health
Observed combinations and failure evidence for this release
First observed break
v0.21.0 golang.org/x/crypto@v0.20.0
go@1.26
8 FAIL · stage: PROJECT_TEST
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| golang.org/x/crypto | v0.20.0 | FAIL Linked failure observed; version changed across releases | contract passed | 6 project-days |
| golang.org/x/sys | v0.17.0 | FAIL Linked failure observed; version changed across releases | contract passed | 6 project-days |
| golang.org/x/term | v0.17.0 | FAIL Linked failure observed; version changed across releases | builds observed | 6 project-days |
| golang.org/x/text | v0.14.0 | FAIL Linked failure observed; version changed across releases | contract passed | 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.
| Library | v0.58.0 | v0.57.0 | v0.55.0 | v0.53.0 | v0.52.0 | v0.51.0 | v0.50.0 | v0.37.0 | v0.35.0 | v0.34.0 | v0.29.0 | v0.21.0 | v0.17.0 | v0.12.0 | v0.4.0 | v0.0.0-20210525063256-abc453219eb5 | v0.0.0-20200625001655-4c5254603344 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| golang.org/x/crypto | v0.55.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.27.0 | v0.20.0 | v0.14.0 | v0.11.0 | — | — | v0.0.0-20200622213623-75b288015ac9 |
| golang.org/x/sys | 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.30.0 | v0.29.0 | v0.25.0 | v0.17.0 | v0.13.0 | v0.10.0 | v0.47.0 | v0.47.0 | v0.0.0-20210603081109-ebe580a85c40 |
| golang.org/x/term | 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.24.0 | v0.17.0 | v0.13.0 | v0.10.0 | — | v0.0.0-20201126162022-7de9c90e9dd1 | — |
| golang.org/x/text | v0.41.0 | v0.40.0 | v0.37.0 | v0.36.0 | v0.35.0 | v0.34.0 | v0.34.0 | v0.23.0 | v0.22.0 | v0.21.0 | v0.18.0 | v0.14.0 | v0.13.0 | v0.11.0 | v0.5.0 | v0.3.6 | v0.3.2 |
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
-
observed PROJECT_TEST Evidence gap ×8 v0.12.0 → v0.21.0 → v0.29.0 → v0.51.0 → v0.55.0 runtime=go@1.26Evidence quality: legacy-evidence-incomplete · Environment variants: 3 · First recorded: 2026-08-17 · Last seen: 2026-08-30Diagnostic re-verification candidate