Recordsgolanggolang.org/x/cryptov0.52.0
Change the conditions
Current conditions
golang.org/x/crypto @v0.52.0windows 11 · x64 · go 1.26 · go 1
package-level total, not an API
11 of 13 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 (4)
- Project observations
- 11 / 13
- Contract verifications
- nothing at this coordinate
- Independent reporting peers
- 1
- Failures with a captured fingerprint
- 0 / 2
- Last recorded
- 2026-08-18
Dependency Health
Observed combinations and failure evidence for this release
First observed break
v0.52.0
windows · go@1.26
3 FAIL · stage: PROJECT_TEST
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| golang.org/x/net | v0.54.0 | CANDIDATE Correlated change; unproven combination | nothing measured | 3 project-days |
| golang.org/x/net | v0.55.0 | CANDIDATE Correlated change; unproven combination | contract passed | 2 project-days |
| golang.org/x/sys | v0.45.0 | CANDIDATE Correlated change; unproven combination | contract passed | 5 project-days |
| golang.org/x/term | v0.43.0 | CANDIDATE Correlated change; unproven combination | contract passed | 5 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: 3 · 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 ×3 v0.48.0 → v0.52.0 os=windows · runtime=go@1.26Evidence quality: legacy-evidence-incomplete · Environment variants: 1 · First recorded: 2026-08-17 · Last seen: 2026-08-17Diagnostic re-verification candidate