CodeSampleX

Recordsgolanggithub.com/stretchr/testify

Change the conditions
Fixed
OSubuntu glibc Package versionv1.9.0
Filter Runtimego 1.26 Architecturex64 Package managergo 1 libcglibc Clear filters

Current conditions

github.com/stretchr/testify @v1.9.0ubuntu glibc · x64 · go 1.26 · go 1

2 of 2 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
2 / 2
Contract verifications
nothing at this coordinate
Usage records
1
Independent reporting peers
1
Last recorded
2026-09-16

Exact records

This slice is down to its measured combinations — the environments below are exactly what ran.

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.1 CHANGED Version changed, no linked failure contract passed 7 project-days
github.com/pmezard/go-difflib v1.0.0 CHANGED Version changed, no linked failure contract passed 7 project-days
github.com/stretchr/objx v0.1.0 CHANGED Version changed, no linked failure contract passed 1 project-day
github.com/stretchr/objx v0.5.2 CHANGED Version changed, no linked failure builds observed 1 project-day
gopkg.in/yaml.v3 v3.0.1 CHANGED Version changed, no linked failure contract passed 7 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.