CodeSampleX

Recordsgolanggithub.com/stretchr/testifyv1.10.0

Change the conditions
Fixed
Package versionv1.10.0 Package managergo
Filter OSdebian glibc Runtimego 1.26 Symbolwhole package Architecturex64 Execution contextgo libcglibc Clear filters

Current conditions

github.com/stretchr/testify @v1.10.0debian glibc · x64 · go 1.26 · go · go

package-level total, not an API

Recorded as present in projects. Nothing was run at this coordinate.

Observed — real project builds reported from this coordinate.

no sample at this coordinate yet

Project observations
nothing at this coordinate
Contract verifications
nothing at this coordinate
Usage records
14
Independent reporting peers
1
Last recorded
2026-10-24

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 3 · Steady 0

First observed break

v1.10.0

linux · go@1.26

1 FAIL · stage: PROJECT_TEST · fingerprint: sha256:943c460a4a7e8c85f76c1aa6a5c18d93f62bf3cfeed5fe56730287702c24d8c5

Library Version Health Measured there Projects
github.com/davecgh/go-spew v1.1.1 CANDIDATE Correlated change; unproven combination contract passed 93 project-days
github.com/pmezard/go-difflib v1.0.0 CANDIDATE Correlated change; unproven combination contract passed 93 project-days
gopkg.in/yaml.v3 v3.0.1 CANDIDATE Correlated change; unproven combination contract passed 93 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