CodeSampleX

Recordsgolanggithub.com/jackc/pgservicefilev0.0.0-20240606120523-5a60cdf6a761

Change the conditions
Fixed
OSdebian glibc Package versionv0.0.0-20240606120523-5a60cdf6a761
Filter Runtimego 1.26 Symbolwhole package Architecturex64 Package managergo Execution contextgo libcglibc Clear filters

Current conditions

github.com/jackc/pgservicefile @v0.0.0-20240606120523-5a60cdf6a761debian 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.

there is a sample here, and nothing of ours has run it at this coordinate yet (1)

Project observations
nothing at this coordinate
Contract verifications
nothing at this coordinate
Usage records
4
Independent reporting peers
2
Last recorded
2026-09-13
Evidence you can open

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 2 · Steady 0

First observed break

v0.0.0-20240606120523-5a60cdf6a761

windows · go@1.26

272 FAIL · stage: PROJECT_TEST

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

Libraryv0.0.0-20240606120523-5a60cdf6a761v0.0.0-20221227161230-091c0ba34f0av0.0.0-20200714003250-2b9c44734f2b
github.com/stretchr/testify v1.11.1 v1.7.0 v1.5.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.

Recent failure clusters

Showing the 12 most-reported of 22 recorded failure clusters. The rest are single reports.