Recordsgolanggolang.org/x/netv0.46.0
Change the conditions
Current conditions
golang.org/x/net @v0.46.0ubuntu glibc · x64 · go 1.26 · go 1
package-level total, not an API
0 of 5 passed
Verified — this network ran a contract at this coordinate.
there is a sample here, and our run of it at this coordinate failed
- Project observations
- 16 / 19
- Contract verifications
- 0 / 5
- Usage records
- 23
- Independent reporting peers
- 1
- Last recorded
- 2026-10-24
Dependency Health
Observed combinations and failure evidence for this release
First observed break
v0.46.0
linux · go@1.26
14 FAIL
· stage: UNKNOWN
· fingerprint: sha256:3b3190f2cd44c327e0d62d5fcac6e314a022dc126a98b5c1b38661e44ab6a020
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| golang.org/x/crypto | v0.43.0 | CANDIDATE Correlated change; unproven combination | contract passed | 8 project-days |
| golang.org/x/sys | v0.37.0 | CANDIDATE Correlated change; unproven combination | contract passed | 9 project-days |
| golang.org/x/term | v0.36.0 | CANDIDATE Correlated change; unproven combination | nothing measured | 8 project-days |
| golang.org/x/text | v0.30.0 | CANDIDATE Correlated change; unproven combination | contract passed | 8 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 UNKNOWN exit 1 Evidence gap ×14 v0.0.0-20210119194325-5f4716e94777 → v0.0.0-20210503060351-7fd8e65b6420 → v0.12.0 → v0.17.0 → v0.38.0 → v0.46.0 → v0.52.0 os=linux · runtime=go@1.26 sha256:3b3190f2cd44…doc: cannot find package <str> in any of: · ($GOROOT not set) · <path> (from $GOPATH)go · unclassified-diagnostic · outer go · gap stage-unknownEvidence quality: complete · Environment variants: 1 · First recorded: 2026-08-30 · Last seen: 2026-10-24Diagnostic re-verification candidate
-
observed UNKNOWN exit 1 Evidence gap ×13 v0.0.0-20180906233101-161cd47e91fd → v0.0.0-20181023162649-9b4f9f5ad519 → v0.0.0-20181108082009-03003ca0c849 → v0.0.0-20190311183353-d8887717615a → v0.0.0-20190620200207-3b0461eec859 → v0.0.0-20191119073136-fc4aabc6c914 → v0.0.0-20200202094626-16171245cfb2 → v0.0.0-20200324143707-d3edc9973b7e → v0.0.0-20200822124328-c89045814202 → v0.0.0-20210503060351-7fd8e65b6420 → v0.2.0 → v0.41.0 → v0.46.0 os=linux · runtime=go@1.26 sha256:0882784d80c2…go: build output <str> already exists and is a directorygo · unclassified-diagnostic · outer go build · gap stage-unknownEvidence quality: complete · Environment variants: 1 · First recorded: 2026-10-15 · Last seen: 2026-10-30Diagnostic re-verification candidate