CodeSampleX

Recordsgolanggithub.com/google/go-cmpv0.4.0

Change the conditions
Fixed
Package versionv0.4.0 Symbolwhole package Package managergo
Filter OSdebian glibc Runtimego 1.26 Architecturex64 Execution contextgo libcglibc Clear filters

Current conditions

github.com/google/go-cmp @v0.4.0debian glibc · x64 · go 1.26 · go · go

package-level total, not an API

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
4 / 4
Contract verifications
1 / 1
Usage records
3
Independent reporting peers
1
Last recorded
2026-09-05
Evidence you can open

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Steady 1

First observed break

v0.4.0

linux · go@1.26

2 FAIL · stage: UNKNOWN · fingerprint: sha256:042f6e977a16262a7e633b3137ce9291be598b66496d9201e447ee2b8efa6eb8

View exact conditions View failure cluster
Library Version Health Measured there Projects
golang.org/x/xerrors v0.0.0-20191204190536-9bdfabe68543 PASS All observations passed contract passed 11 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.

Libraryv0.5.5v0.5.4v0.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.

Recent failure clusters