Recordsgolanggithub.com/google/go-cmp
Change the conditions
Current conditions
github.com/google/go-cmp/cmp.Comparer @v0.5.5glibc · x64 · go 1.26 · 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 (1)
- Project observations
- 1 / 1
- Contract verifications
- 1 / 1
- Independent reporting peers
- 1
- Last recorded
- 2026-09-03
Exact records
This slice is down to its measured combinations — the environments below are exactly what ran.
-
debian glibc · x64 · go 1.26 · go · go
1 of 1 passed
Verified — this network ran a contract at this coordinate.
-
ubuntu glibc · x64 · go 1.26 · go 1
1 of 1 passed
Observed — real project builds reported from this coordinate.
Dependency Health
Observed combinations and failure evidence for this release
First observed break
v0.5.5
linux · go@1.26
1 FAIL
· stage: PROJECT_COMPILE
· fingerprint: sha256:d5fae02e8604b6955b8f1c65a8d5cc795aaceed9651a9f67da2c34536a6764a1
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| golang.org/x/xerrors | v0.0.0-20191204190536-9bdfabe68543 | PASS All observations passed | contract passed | 54 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.
| Library | v0.5.5 | v0.5.4 | v0.4.0 |
|---|---|---|---|
| golang.org/x/xerrors | v0.0.0-20191204190536-9bdfabe68543 | v0.0.0-20191204190536-9bdfabe68543 | v0.0.0-20191204190536-9bdfabe68543 |
Moved: 0 · unchanged at every release: 1
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.