CodeSampleX

Recordsgolanggithub.com/google/go-cmpv0.5.1cmp.Equal

Change the conditions
Fixed
Symbolcmp.Equal Architecturex64
Filter OSdebian glibc Runtimego 1.26 Package versionv0.5.1 Package managergo Execution contextgo libcglibc Clear filters

Current conditions

cmp.Equal @v0.5.1debian glibc · x64 · go 1.26 · go · 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-10-16

Dependency Health

Observed combinations and failure evidence for this release

Changed 1 · Steady 0

Dependency changes observed: 1. No failure evidence is linked to these resolved trees yet.

Library Version Health Measured there Projects
golang.org/x/xerrors v0.0.0-20191204190536-9bdfabe68543 CHANGED Version changed, no linked failure contract passed 5 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.