Recordsnpmpg8.23.0pg.PoolClient
Change the conditions
Current conditions
pg.PoolClient @8.23.0windows 11 · x64 · node 24 · npm 11 · node
0 of 22 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
- 64 / 75
- Contract verifications
- 0 / 22
- Independent reporting peers
- 1
- Last recorded
- 2026-09-14
Evidence you can open
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.
| Library | 8.23.0 | 8.16.3 |
|---|---|---|
| pg-connection-string | 2.14.0 | 2.9.1 |
| pg-pool | 3.14.0 | 3.10.1 |
| pg-protocol | 1.16.0 | 1.10.3 |
| pg-types | 2.2.0 | 2.2.0 |
| pgpass | 1.0.5 | 1.0.5 |
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
-
observed PROCESS_START process start failed Evidence gap ×3 8.23.0 executionContext=node sha256:c12549970456…· structured-termination · gap diagnostic-missingEvidence quality: partial · Environment variants: 2 · First recorded: 2026-09-02 · Last seen: 2026-09-13Diagnostic re-verification candidate
-
observed UNKNOWN exit 1 ERR_ASSERTION Evidence gap ×2 8.23.0 executionContext=node · moduleSystem=esm · os=windows · runtime=node@24.13 pg.PoolClient sha256:340c5f78ca35…Image hunterzo-egress-lab:local Building · Image hunterzo-egress-lab:local Built · Network hunterzo-egress-lab_fixture_net Creating …· unclassified-diagnostic · gap stage-unknownEvidence quality: complete · Environment variants: 1 · First recorded: 2026-09-14 · Last seen: 2026-09-14Diagnostic re-verification candidate
-
observed PROJECT_COMPILE exit 1 TS7006 ×1 8.23.0 executionContext=node · moduleSystem=esm · os=windows · runtime=node@24.13 pg.PoolClient sha256:341e6d7780ec…src/egress.ts(<n>,<n>): error TS7006: Parameter <str> implicitly has an <str> type. …typescript/tsc · compiler-diagnostic · outer npm runEvidence quality: complete · Environment variants: 1 · First recorded: 2026-09-13 · Last seen: 2026-09-13
-
observed PROJECT_COMPILE exit 1 TS7034 ×1 8.23.0 executionContext=node · moduleSystem=esm · os=windows · runtime=node@24.13 pg.PoolClient sha256:85a890982324…tests/crawl-budget.test.ts(<n>,<n>): error TS7034: Variable <str> implicitly has type <str> in some locations where its type cannot be determined.typescript/tsc · compiler-diagnostic · outer npm runEvidence quality: complete · Environment variants: 1 · First recorded: 2026-09-13 · Last seen: 2026-09-13
-
observed PROJECT_COMPILE exit 1 TS7005 ×1 8.23.0 executionContext=node · moduleSystem=esm · os=windows · runtime=node@24.13 pg.PoolClient sha256:8dabe9f19999…src/worker.ts(<n>,<n>): error TS7005: Variable <str> implicitly has an <str> type. …typescript/tsc · compiler-diagnosticEvidence quality: complete · Environment variants: 1 · First recorded: 2026-09-13 · Last seen: 2026-09-13
-
observed PROJECT_COMPILE exit 1 TS7005 ×1 8.23.0 executionContext=node · moduleSystem=esm · os=windows · runtime=node@24.13 pg.PoolClient sha256:9157cca40f14…tests/crawl-budget.test.ts(<n>,<n>): error TS7005: Variable <str> implicitly has an <str> type.typescript/tsc · compiler-diagnostic · outer npm runEvidence quality: complete · Environment variants: 1 · First recorded: 2026-09-13 · Last seen: 2026-09-13
-
observed PROJECT_COMPILE exit 1 TS7034 ×1 8.23.0 executionContext=node · moduleSystem=esm · os=windows · runtime=node@24.13 pg.PoolClient sha256:ac624b80f496…src/worker.ts(<n>,<n>): error TS7034: Variable <str> implicitly has type <str> in some locations where its type cannot be determined.typescript/tsc · compiler-diagnosticEvidence quality: complete · Environment variants: 1 · First recorded: 2026-09-13 · Last seen: 2026-09-13
-
observed PROJECT_COMPILE exit 1 TS2882 ×1 8.23.0 executionContext=node · moduleSystem=esm · os=windows · runtime=node@24.13 pg.PoolClient sha256:afb09a3a1b84…ui/main.tsx(<n>,<n>): error TS2882: Cannot find module or type declarations for side-effect import of <str>.typescript/tsc · compiler-diagnosticEvidence quality: complete · Environment variants: 1 · First recorded: 2026-09-13 · Last seen: 2026-09-13
-
observed PROJECT_COMPILE exit 1 TS2554 ×1 8.23.0 executionContext=node · moduleSystem=esm · os=windows · runtime=node@24.13 pg.PoolClient sha256:b069f147418d…src/egress.ts(<n>,<n>): error TS2554: Expected 2 arguments, but got 3.typescript/tsc · compiler-diagnostic · outer npm runEvidence quality: complete · Environment variants: 1 · First recorded: 2026-09-13 · Last seen: 2026-09-13
-
observed PROJECT_COMPILE exit 1 TS2352 ×1 8.23.0 executionContext=node · moduleSystem=esm · os=windows · runtime=node@24.13 pg.PoolClient sha256:c6b452f5bad2…tests/core.test.ts(<n>,<n>): error TS2352: Conversion of type <str> to type <str> may be a mistake because neither type sufficiently overlaps with the other. …typescript/tsc · compiler-diagnosticEvidence quality: complete · Environment variants: 1 · First recorded: 2026-09-13 · Last seen: 2026-09-13
-
observed PROJECT_COMPILE exit 1 TS2349 ×1 8.23.0 executionContext=node · moduleSystem=esm · os=windows · runtime=node@24.13 pg.PoolClient sha256:d6c915113d6a…src/crawl-policy.ts(<n>,<n>): error TS2349: This expression is not callable.typescript/tsc · compiler-diagnostic · outer npm runEvidence quality: complete · Environment variants: 1 · First recorded: 2026-09-13 · Last seen: 2026-09-13
-
observed PROJECT_TEST exit 1 ERR_ASSERTION ×1 8.23.0 executionContext=node · moduleSystem=esm · os=windows · runtime=node@24.13 pg.PoolClient sha256:0cab186a142b…AssertionError [ERR_ASSERTION]: Expected values to be strictly equal: · 2 !== 0 · at TestContext.<anonymous> (<url>) …javascript/test-runner · test-runner-diagnosticEvidence quality: complete · Environment variants: 1 · First recorded: 2026-09-13 · Last seen: 2026-09-13
Showing the 12 most-reported of 33 recorded failure clusters. The rest are single reports.