CodeSampleX

Recordsgolanggithub.com/jackc/puddlev1.3.0

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

Current conditions

github.com/jackc/puddle @v1.3.0ubuntu glibc · x64 · go 1.26 · go 1

package-level total, not an API

0 of 1 passed

Verified — this network ran a contract at this coordinate.

there is a sample here, and our run of it at this coordinate failed (2)

Project observations
4 / 4
Contract verifications
0 / 1
Usage records
6
Independent reporting peers
1
Last recorded
2026-09-16
Evidence you can open

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 2 · Steady 0

First observed break

v1.3.0

linux · go@1.26

1 FAIL · stage: UNKNOWN · fingerprint: sha256:9fe0e5655146d3ab444a3d385ac7757a2fd3221661c815acd965cd7df23e100f

View exact conditions View failure cluster
Library Version Health Measured there Projects
github.com/stretchr/testify v1.3.0 CANDIDATE Correlated change; unproven combination contract passed 2 project-days
github.com/stretchr/testify v1.8.1 CANDIDATE Correlated change; unproven combination contract passed 8 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.

Libraryv1.3.0v1.1.3v0.0.0-20190608224051-11cab39313c9
github.com/stretchr/testify v1.3.0 v1.3.0 v1.7.0

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.

Recent failure clusters