CodeSampleX

Recordsgolanggithub.com/stretchr/testifyv1.12.1

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

Current conditions

github.com/stretchr/testify @v1.12.1debian 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
11
Independent reporting peers
1
Last recorded
2026-10-12

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 1 · Steady 1

First observed break

v1.12.1

linux · go@1.26

1 FAIL · stage: PROJECT_COMPILE · fingerprint: sha256:bed685930873883c4ef3e80f9aa41f1a7c1e3a2c11579d314102313e7bd6ebf5

Library Version Health Measured there Projects
github.com/stretchr/objx v0.5.3 CANDIDATE Correlated change; unproven combination builds observed 1 project-day
go.yaml.in/yaml/v3 v3.0.5 PASS All observations passed contract passed 52 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