CodeSampleX

Recordsgolanggithub.com/stretchr/testifyv1.4.0github.com/stretchr/testify/assert.Nil

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

Current conditions

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

3 of 3 passed

Observed — real project builds reported from this coordinate.

no sample at this coordinate yet

Project observations
3 / 3
Contract verifications
nothing at this coordinate
Independent reporting peers
1
Last recorded
2026-09-04
Evidence you can open

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 9 · Steady 0

First observed break

v1.4.0

linux · go@1.26

1 FAIL · stage: UNKNOWN · fingerprint: sha256:6ab050d4d4b1a7c9fde83bf5cb81c7f5e71fb06a2d34da1bf7b8e6d7e8d53dcc

View exact conditions View failure cluster
Library Version Health Measured there Projects
github.com/davecgh/go-spew v1.1.0 CANDIDATE Correlated change; unproven combination contract passed 9 project-days
github.com/davecgh/go-spew v1.1.1 CANDIDATE Correlated change; unproven combination contract passed 29 project-days
github.com/pmezard/go-difflib v1.0.0 CANDIDATE Correlated change; unproven combination contract passed 38 project-days
github.com/stretchr/objx v0.1.0 CANDIDATE Correlated change; unproven combination contract passed 13 project-days
github.com/stretchr/objx v0.1.1 CANDIDATE Correlated change; unproven combination nothing measured 18 project-days
github.com/stretchr/objx v0.2.0 CANDIDATE Correlated change; unproven combination contract passed 4 project-days
gopkg.in/yaml.v2 v2.2.2 CANDIDATE Correlated change; unproven combination contract passed 17 project-days
gopkg.in/yaml.v2 v2.3.0 CANDIDATE Correlated change; unproven combination contract passed 16 project-days
gopkg.in/yaml.v2 v2.4.0 CANDIDATE Correlated change; unproven combination 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.

Libraryv1.12.1v1.11.1v1.10.0v1.9.0v1.8.4v1.8.1v1.8.0v1.7.5v1.7.1v1.7.0v1.6.1v1.5.1v1.4.0v1.3.0
github.com/davecgh/go-spew — v1.1.2-0.20180830191138-d8f796af33cc v1.1.1 v1.1.1 v1.1.1 v1.1.1 v1.1.1 v1.1.1 v1.1.0 v1.1.0 v1.1.1 v1.1.1 v1.1.0 v1.1.1
github.com/pmezard/go-difflib — v1.0.1-0.20181226105442-5d4384ee4fb2 v1.0.0 v1.0.0 v1.0.0 v1.0.0 v1.0.0 v1.0.0 v1.0.0 v1.0.0 v1.0.0 v1.0.0 v1.0.0 v1.0.0
github.com/stretchr/objx v0.5.3 v0.5.2 — v0.5.2 v0.5.3 v0.2.0 v0.4.0 v0.4.0 v0.1.0 v0.2.0 v0.1.0 v0.1.0 v0.2.0 v0.2.0
gopkg.in/yaml.v2 — — — — — — — — — — — v2.3.0 v2.4.0 —
gopkg.in/yaml.v3 — v3.0.1 v3.0.1 v3.0.1 v3.0.1 v3.0.1 v3.0.1 v3.0.1 v3.0.0-20210107192922-496545a6307b v3.0.1 v3.0.1 — — —
go.yaml.in/yaml/v3 v3.0.5 — — — — — — — — — — — — —

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.

Recent failure clusters