CodeSampleX

Recordsgolanggithub.com/stretchr/testifyv1.3.0github.com/stretchr/testify/assert.False

Change the conditions
Fixed
Package versionv1.3.0 Symbolgithub.com/stretchr/testify/assert.False
Filter OSubuntu glibc Runtimego 1.26 Architecturex64 Package managergo 1 libcglibc Clear filters

Current conditions

github.com/stretchr/testify/assert.False @v1.3.0ubuntu glibc · x64 · go 1.26 · go 1

4 of 4 passed

Observed — real project builds reported from this coordinate.

no sample at this coordinate yet

Project observations
4 / 4
Contract verifications
nothing at this coordinate
Independent reporting peers
1
Last recorded
2026-09-05

Dependency Health

Observed combinations and failure evidence for this release

Changed 5 · Steady 0

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

Library Version Health Measured there Projects
github.com/davecgh/go-spew v1.1.0 CHANGED Version changed, no linked failure contract passed 17 project-days
github.com/davecgh/go-spew v1.1.1 CHANGED Version changed, no linked failure contract passed 18 project-days
github.com/pmezard/go-difflib v1.0.0 CHANGED Version changed, no linked failure contract passed 35 project-days
github.com/stretchr/objx v0.1.0 CHANGED Version changed, no linked failure contract passed 33 project-days
github.com/stretchr/objx v0.2.0 CHANGED Version changed, no linked failure contract passed 2 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: 5 · 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.