Recordsgolanggithub.com/google/go-cmpv0.5.0github.com/google/go-cmp/cmp.Option
Change the conditions
Current conditions
github.com/google/go-cmp/cmp.Option @v0.5.0ubuntu glibc · x64 · go 1.26 · go 1
2 of 2 passed
Observed — real project builds reported from this coordinate.
no sample at this coordinate yet
- Project observations
- 2 / 2
- Contract verifications
- nothing at this coordinate
- Independent reporting peers
- 1
- Last recorded
- 2026-10-17
Dependency Health
Observed combinations and failure evidence for this release
First observed break
v0.5.0
linux · go@1.26
1 FAIL
· stage: UNKNOWN
· fingerprint: sha256:0882784d80c20e919569b4a9a1a5ff54eb0aa7665750aedc7afd0bce723472f8
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| golang.org/x/xerrors | v0.0.0-20191204190536-9bdfabe68543 | CANDIDATE Correlated change; unproven combination | contract passed | 18 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.0 os=linux · runtime=go@1.26 sha256:0882784d80c2…go: build output <str> already exists and is a directorygo · unclassified-diagnostic · outer go build · gap stage-unknownEvidence quality: complete · Environment variants: 1 · First recorded: 2026-10-17 · Last seen: 2026-10-17Diagnostic re-verification candidate