Recordsgolanggithub.com/google/go-cmpv0.5.1cmp.Diff
Change the conditions
Current conditions
cmp.Diff @v0.5.1debian glibc · x64 · go 1.26 · go · go
1 of 1 passed
Verified — this network ran a contract at this coordinate.
there is a sample here, and our run of it at this coordinate came back clean (2)
- Project observations
- 2 / 2
- Contract verifications
- 1 / 1
- Independent reporting peers
- 1
- Last recorded
- 2026-10-19
Dependency Health
Observed combinations and failure evidence for this release
First observed break
v0.5.1
linux · go@1.26
1 FAIL
· stage: UNKNOWN
· fingerprint: sha256:2e190e692db4a238348d518071f638bb22dbc94a247a3d61571672864229db70
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| golang.org/x/xerrors | v0.0.0-20191204190536-9bdfabe68543 | CANDIDATE Correlated change; unproven combination | contract passed | 9 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: 1 · 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 ×1 v0.5.1 os=linux · runtime=go@1.26 sha256:2e190e692db4…panic: ambiguous set of applicable options at {string}: · Transformer(Trim, strings.TrimSpace) · Comparer(main.verifyCmpDiff.func2) …go · unclassified-diagnostic · outer go run · gap stage-unknownEvidence quality: complete · Environment variants: 1 · First recorded: 2026-10-16 · Last seen: 2026-10-16Diagnostic re-verification candidate