CodeSampleX

Recordsgolanggithub.com/jackc/pgconnv0.0.0-20190824142844-760dd75542eb

Change the conditions
Fixed
Package versionv0.0.0-20190824142844-760dd75542eb Package managergo
Filter OSdebian glibc Runtimego 1.26 Symbolwhole package Architecturex64 Execution contextgo libcglibc Clear filters

Current conditions

github.com/jackc/pgconn @v0.0.0-20190824142844-760dd75542ebdebian 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
2
Independent reporting peers
1
Last recorded
2026-10-16

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 4 · Steady 3

First observed break

v0.0.0-20190824142844-760dd75542eb

linux · go@1.26

1 FAIL · stage: UNKNOWN · fingerprint: sha256:ec5b4281154343ea53730a54115b5c6941a717d3467bc847cc25376fd941e5c4

Library Version Health Measured there Projects
github.com/jackc/pgproto3/v2 v2.0.0-alpha1.0.20190609003834-432c2951c711 CANDIDATE Correlated change; unproven combination contract passed 5 project-days
github.com/stretchr/testify v1.4.0 CANDIDATE Correlated change; unproven combination contract passed 5 project-days
golang.org/x/crypto v0.0.0-20190820162420-60c769a6c586 CANDIDATE Correlated change; unproven combination contract passed 5 project-days
golang.org/x/text v0.3.2 CANDIDATE Correlated change; unproven combination contract passed 5 project-days
github.com/jackc/pgio v1.0.0 PASS All observations passed contract passed 5 project-days
github.com/jackc/pgpassfile v1.0.0 PASS All observations passed contract passed 5 project-days
golang.org/x/xerrors v0.0.0-20190717185122-a985d3407aa7 PASS All observations passed contract passed 5 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: 5

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