CodeSampleX

Recordsgolanggithub.com/stretchr/testifyv1.8.1github.com/stretchr/testify/assert.ElementsMatch

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

Current conditions

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

5 of 5 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 (1)

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

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 6 · Steady 0

First observed break

v1.8.1

linux · go@1.26

1 FAIL · stage: UNKNOWN · fingerprint: sha256:042f6e977a16262a7e633b3137ce9291be598b66496d9201e447ee2b8efa6eb8

Library Version Health Measured there Projects
github.com/davecgh/go-spew v1.1.1 CANDIDATE Correlated change; unproven combination contract passed 53 project-days
github.com/pmezard/go-difflib v1.0.0 CANDIDATE Correlated change; unproven combination contract passed 53 project-days
github.com/stretchr/objx v0.1.0 CANDIDATE Correlated change; unproven combination contract passed 7 project-days
github.com/stretchr/objx v0.2.0 CANDIDATE Correlated change; unproven combination contract passed 1 project-day
github.com/stretchr/objx v0.5.0 CANDIDATE Correlated change; unproven combination contract passed 21 project-days
gopkg.in/yaml.v3 v3.0.1 CANDIDATE Correlated change; unproven combination contract passed 53 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.

Recent failure clusters