CodeSampleX

Recordsgolanggithub.com/stretchr/objx

Change the conditions
Fixed
OSdebian glibc Package versionv0.5.2
Filter Runtimego 1.26 Architecturex64 Package managergo Execution contextgo libcglibc Clear filters

Current conditions

github.com/stretchr/objx @v0.5.2debian glibc · x64 · go 1.26 · go · go

2 of 2 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 (2)

Project observations
8 / 8
Contract verifications
2 / 2
Usage records
4
Independent reporting peers
1
Last recorded
2026-10-13

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 2 · Steady 0

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

Library Version Health Measured there Projects
github.com/stretchr/testify v1.11.1 CHANGED Version changed, no linked failure contract passed 5 project-days
github.com/stretchr/testify v1.8.4 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.

Libraryv0.5.2v0.5.0v0.4.0v0.2.0
github.com/stretchr/testify v1.8.4 v1.8.4 v1.8.0 v1.8.1

Moved: 1 · unchanged at every release: 0

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.