Recordsgolanggolang.org/x/netv0.52.0
Change the conditions
Current conditions
golang.org/x/net @v0.52.0linux · glibc · x64 · go 1.26 · go 1
package-level total, not an API
0 of 21 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
- 192 / 210
- Contract verifications
- 0 / 21
- Usage records
- 101
- Independent reporting peers
- 3
- Last recorded
- 2026-09-01
Dependency Health
Observed combinations and failure evidence for this release
First observed break
v0.52.0
linux
31 FAIL
· stage: UNKNOWN
· fingerprint: sha256:9be950af9140edade9f2c5aa029896fb7dd194960195369ee277ef42a11d6868
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| golang.org/x/crypto | v0.49.0 | CANDIDATE Correlated change; unproven combination | nothing measured | 17 project-days |
| golang.org/x/sys | v0.42.0 | CANDIDATE Correlated change; unproven combination | contract passed | 17 project-days |
| golang.org/x/term | v0.41.0 | CANDIDATE Correlated change; unproven combination | nothing measured | 17 project-days |
| golang.org/x/text | v0.35.0 | CANDIDATE Correlated change; unproven combination | contract passed | 17 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 ×31 v0.0.0-20220403103023-749bd193bc2b → v0.17.0 → v0.37.0 → v0.52.0 os=linux sha256:9be950af9140…Traceback (most recent call last): · File <str>, line 1, in <module> · ModuleNotFoundError: No module named <str>python3 · unclassified-diagnostic · outer python3 · gap stage-unknownEvidence quality: complete · Environment variants: 2 · First recorded: 2026-08-30 · Last seen: 2026-09-02Diagnostic re-verification candidate
-
observed PROJECT_COMPILE exit 1 ×5 v0.24.0 → v0.50.0 → v0.52.0 os=linux · runtime=go@1.26 sha256:d5fae02e8604…test/contract.go:<n>:<n>: <str> imported and not usedgo/compiler · compiler-diagnostic · outer go runEvidence quality: complete · Environment variants: 1 · First recorded: 2026-08-31 · Last seen: 2026-09-05
-
observed UNKNOWN exit 1 ERROR Evidence gap ×5 v0.52.0 os=linux · runtime=go@1.26 sha256:69d280c75213…verifying go.opentelemetry.io/otel@v1.43.0/go.mod: checksum mismatch · downloaded: h1:<token> · go.sum: h1:<token> · SECURITY ERRORgo · unclassified-diagnostic · outer go mod, go run · gap stage-unknownEvidence quality: complete · Environment variants: 1 · First recorded: 2026-08-31 · Last seen: 2026-09-01Diagnostic re-verification candidate
-
observed PROJECT_COMPILE exit 1 ×4 v0.12.0 → v0.52.0 → v0.56.0 os=linux · runtime=go@1.26 sha256:964ddac6b19a…<path> <str> imported and not usedgo/compiler · compiler-diagnostic · outer go runEvidence quality: complete · Environment variants: 1 · First recorded: 2026-08-30 · Last seen: 2026-09-05