Recordsgolanggolang.org/x/netv0.52.0
Change the conditions
Current conditions
golang.org/x/net @v0.52.0ubuntu glibc · x64 · node 22 · npm · node
package-level total, not an API
1 of 1 passed
Observed — real project builds reported from this coordinate.
no sample at this coordinate yet
- Project observations
- 1 / 1
- Contract verifications
- nothing at this coordinate
- Usage records
- 1
- Independent reporting peers
- 1
- Last recorded
- 2026-09-01
Dependency Health
Observed combinations and failure evidence for this release
First observed break
v0.52.0 golang.org/x/crypto@v0.49.0
linux
31 FAIL
· stage: UNKNOWN
· fingerprint: sha256:9be950af9140edade9f2c5aa029896fb7dd194960195369ee277ef42a11d6868
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| golang.org/x/crypto | v0.49.0 | FAIL Linked failure observed; version changed across releases | nothing measured | 17 project-days |
| golang.org/x/sys | v0.42.0 | FAIL Linked failure observed; version changed across releases | contract passed | 17 project-days |
| golang.org/x/term | v0.41.0 | FAIL Linked failure observed; version changed across releases | nothing measured | 17 project-days |
| golang.org/x/text | v0.35.0 | FAIL Linked failure observed; version changed across releases | 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 UNKNOWN exit 1 Evidence gap ×7 v0.0.0-20220403103023-749bd193bc2b → v0.17.0 → v0.37.0 → v0.52.0 executionContext=node · moduleSystem=cjs · os=linux · runtime=node@22.23 sha256:72ba2d1e946f…<path>: No module named pippython3 · unclassified-diagnostic · outer python3 · gap stage-unknownEvidence quality: complete · Environment variants: 1 · First recorded: 2026-08-30 · Last seen: 2026-09-02Diagnostic re-verification candidate
-
observed PROCESS_START process start failed Evidence gap ×4 v0.37.0 → v0.43.0 → v0.52.0 executionContext=node · os=linux · runtime=node@22.23 sha256:c12549970456…· structured-termination · gap diagnostic-missingEvidence quality: partial · Environment variants: 2 · First recorded: 2026-08-31 · Last seen: 2026-09-02Diagnostic re-verification candidate
-
observed UNKNOWN exit 2 EVERYTHING Evidence gap ×3 v0.0.0-20220403103023-749bd193bc2b → v0.52.0 executionContext=node · moduleSystem=cjs · os=linux · runtime=node@22.23 sha256:d29a2deca319…csx sample: unknown subcommand <str> · usage: csx sample <subcommand> · propose --goal G [--package purl]... [--symbol s]... …· unclassified-diagnostic · gap stage-unknownEvidence quality: complete · Environment variants: 1 · First recorded: 2026-08-30 · Last seen: 2026-09-02Diagnostic re-verification candidate