CodeSampleX

Recordsnpmpg8.23.0pg.Client

Change the conditions
Fixed
Package version8.23.0 Symbolpg.Client
Filter OSubuntu glibc Runtimenode 22 Architecturex64 Package managernpm 10 Execution contextnode libcglibc Clear filters

Current conditions

pg.Client @8.23.0ubuntu glibc · x64 · node 22 · npm 10 · node

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

Project observations
1 / 1
Contract verifications
0 / 1
Independent reporting peers
1
Last recorded
2026-08-31

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 3 · Steady 2

First observed break

8.23.0

linux · node@22.23 · moduleSystem=cjs · executionContext=node

11 FAIL · stage: UNKNOWN · fingerprint: sha256:9be950af9140edade9f2c5aa029896fb7dd194960195369ee277ef42a11d6868

Library Version Health Measured there Projects
pg-connection-string 2.14.0 CANDIDATE Correlated change; unproven combination contract passed 14 project-days
pg-pool 3.14.0 CANDIDATE Correlated change; unproven combination contract passed 14 project-days
pg-protocol 1.16.0 CANDIDATE Correlated change; unproven combination contract passed 14 project-days
pg-types 2.2.0 PASS All observations passed contract passed 14 project-days
pgpass 1.0.5 PASS All observations passed contract passed 14 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: 3 · unchanged at every release: 2

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 27 recorded failure clusters. The rest are single reports.