Recordsgolanggolang.org/x/cryptov0.27.0
Change the conditions
Current conditions
golang.org/x/crypto @v0.27.0ubuntu glibc · x64 · node 22 · npm 10 · node
package-level total, not an API
0 of 4 passed
Verified — this network ran a contract at this coordinate.
there is a sample here, and our run of it at this coordinate failed (9)
- Project observations
- 2 / 2
- Contract verifications
- 0 / 4
- Usage records
- 6
- Independent reporting peers
- 2
- Last recorded
- 2026-08-31
Dependency Health
Observed combinations and failure evidence for this release
First observed break
v0.27.0
linux
13 FAIL · stage: PROJECT_PROCESS
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| golang.org/x/net | v0.21.0 | CANDIDATE Correlated change; unproven combination | contract passed | 2 project-days |
| golang.org/x/sys | v0.25.0 | CANDIDATE Correlated change; unproven combination | nothing measured | 2 project-days |
| golang.org/x/term | v0.24.0 | CANDIDATE Correlated change; unproven combination | nothing measured | 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: 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_PROCESS ERR_ASSERTION Evidence gap ×13 v0.0.0-20220331220935-ae2d96664a29 → v0.19.0 → v0.20.0 → v0.26.0 → v0.27.0 → v0.36.0 → v0.54.0 os=linuxEvidence quality: legacy-evidence-incomplete · Environment variants: 2 · First recorded: 2026-08-21 · Last seen: 2026-08-27Diagnostic re-verification candidate
-
observed UNKNOWN exit 1 Evidence gap ×8 v0.0.0-20220331220935-ae2d96664a29 → v0.27.0 → v0.36.0 → v0.50.0 os=linux sha256:91ad26545eb1…node:internal/modules/cjs/loader:<n> · throw err; · ^ · Error: Cannot find module <str>node · unclassified-diagnostic · outer node · gap stage-unknownEvidence quality: complete · Environment variants: 2 · First recorded: 2026-08-30 · Last seen: 2026-09-04Diagnostic re-verification candidate
-
observed UNKNOWN exit 1 ERR_MODULE_NOT_FOUND Evidence gap ×5 v0.0.0-20220331220935-ae2d96664a29 → v0.27.0 executionContext=node · moduleSystem=cjs · os=linux · runtime=node@22.23 sha256:88af852f99a8…node:internal/modules/package_json_reader:<n> · throw new ERR_MODULE_NOT_FOUND(packageName, fileURLToPath(base), null); · ^ …node · unclassified-diagnostic · outer node · gap stage-unknownEvidence quality: complete · Environment variants: 1 · First recorded: 2026-08-29 · Last seen: 2026-08-31Diagnostic re-verification candidate
-
observed UNKNOWN exit 1 Evidence gap ×5 v0.0.0-20220331220935-ae2d96664a29 → v0.27.0 → v0.56.0 os=linux sha256:9922ca80f240…go: <path> already existsgo · unclassified-diagnostic · outer go mod · gap stage-unknownEvidence quality: complete · Environment variants: 2 · First recorded: 2026-08-29 · Last seen: 2026-09-04Diagnostic re-verification candidate