CodeSampleX

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

Change the conditions
Fixed
Package versionv1.5.1 Symbolgithub.com/stretchr/testify/assert.False Package managergo
Filter OSdebian glibc Runtimego 1.26 Architecturex64 Execution contextgo libcglibc Clear filters

Current conditions

github.com/stretchr/testify/assert.False @v1.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
2 / 2
Contract verifications
1 / 1
Independent reporting peers
1
Last recorded
2026-10-13

Dependency Health

Observed combinations and failure evidence for this release

Changed 9 · Steady 0

Dependency changes observed: 9. 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 95 project-days
github.com/davecgh/go-spew v1.1.1 CHANGED Version changed, no linked failure 19 project-days
github.com/pmezard/go-difflib v1.0.0 CHANGED Version changed, no linked failure 116 project-days
github.com/stretchr/objx v0.1.0 CHANGED Version changed, no linked failure 106 project-days
github.com/stretchr/objx v0.2.0 CHANGED Version changed, no linked failure 9 project-days
gopkg.in/yaml.v2 v2.2.2 CHANGED Version changed, no linked failure 85 project-days
gopkg.in/yaml.v2 v2.2.3 CHANGED Version changed, no linked failure 20 project-days
gopkg.in/yaml.v2 v2.2.8 CHANGED Version changed, no linked failure 7 project-days
gopkg.in/yaml.v2 v2.3.0 CHANGED Version changed, no linked failure 3 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.