Recordsgolanggolang.org/x/netv0.55.0
Change the conditions
Current conditions
golang.org/x/net @v0.55.0ubuntu glibc · x64 · go 1.26 · go 1
package-level total, not an API
0 of 1 passed
Verified — this network ran a contract at this coordinate.
there is a sample here, and our run of it at this coordinate failed (1)
- Project observations
- 6 / 8
- Contract verifications
- 0 / 1
- Usage records
- 1
- Independent reporting peers
- 1
- Last recorded
- 2026-08-30
Dependency Health
Observed combinations and failure evidence for this release
First observed break
v0.55.0 golang.org/x/crypto@v0.52.0
go@1.26
8 FAIL · stage: PROJECT_TEST
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| golang.org/x/crypto | v0.52.0 | FAIL Linked failure observed; version changed across releases | contract passed | 2 project-days |
| golang.org/x/sys | v0.45.0 | FAIL Linked failure observed; version changed across releases | contract passed | 2 project-days |
| golang.org/x/term | v0.43.0 | FAIL Linked failure observed; version changed across releases | contract passed | 2 project-days |
| golang.org/x/text | v0.37.0 | FAIL Linked failure observed; version changed across releases | 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.
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