CodeSampleX

Recordsgolanggithub.com/google/go-cmpv0.5.5

Change the conditions
Fixed
OSubuntu glibc Package versionv0.5.5 Symbolwhole package
Filter Runtimego 1.26 Architecturex64 Package managergo 1 libcglibc Clear filters

Current conditions

github.com/google/go-cmp @v0.5.5ubuntu glibc · x64 · go 1.26 · go 1

package-level total, not an API

3 of 4 passed

Observed — real project builds reported from this coordinate.

there is a sample here, and nothing of ours has run it at this coordinate yet (3)

Project observations
3 / 4
Contract verifications
nothing at this coordinate
Usage records
2
Independent reporting peers
1
Last recorded
2026-09-03
Evidence you can open

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Steady 1

First observed break

v0.5.5

linux · go@1.26

1 FAIL · stage: PROJECT_COMPILE · fingerprint: sha256:d5fae02e8604b6955b8f1c65a8d5cc795aaceed9651a9f67da2c34536a6764a1

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 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.

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