Recordsnpmpg
Change the conditions
Current conditions
pg.Pool @8.23.0x64 · node 22 · npm · node
1 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 came back clean (1)
- Project observations
- 1 / 1
- Contract verifications
- 1 / 1
- Independent reporting peers
- 1
- Last recorded
- 2026-08-30
Exact records
This slice is down to its measured combinations — the environments below are exactly what ran.
-
alpine musl · x64 · node 22 · npm · node
1 of 1 passed
Verified — this network ran a contract at this coordinate.
-
ubuntu glibc · x64 · node 22 · npm · node
1 of 1 passed
Observed — real project builds reported from this coordinate.
Dependency Health
Observed combinations and failure evidence for this release
First observed break
8.23.0
linux · node@22.23 · moduleSystem=cjs · executionContext=node
11 FAIL
· stage: UNKNOWN
· fingerprint: sha256:9be950af9140edade9f2c5aa029896fb7dd194960195369ee277ef42a11d6868
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.