Recordsgolanggithub.com/google/go-cmp
Change the conditions
Current conditions
github.com/google/go-cmp @v0.7.0alpine musl · x64 · go 1.26 · go · go
4 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 came back clean (10)
- Project observations
- 4 / 4
- Contract verifications
- 4 / 4
- Usage records
- 2
- Independent reporting peers
- 1
- Last recorded
- 2026-09-05
Exact records
This slice is down to its measured combinations — the environments below are exactly what ran.
-
cmpopts.SortMaps
1 of 1 passed
Verified — this network ran a contract at this coordinate.
-
4 of 4 passed
Verified — this network ran a contract at this coordinate.
Dependency Health
Observed combinations and failure evidence for this release
First observed break
v0.7.0
windows · go@1.26
2 FAIL · stage: PROJECT_TEST
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-20200804184101-5ec99f83aff1 | v0.0.0-20191204190536-9bdfabe68543 | v0.0.0-20191204190536-9bdfabe68543 |
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.