pg
PostgreSQL client - pure javascript & libpq with the same API
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| semgrep | semgrep:base64-decode | AI (semgrep): Base64 decode in sasl.js is standard SCRAM-SHA-256 authentication protocol — decoding a server-provided salt. This is correct cryptographic implementation, not obfuscation. | ai | |
| dependencies | unvetted-dep:pgpass | AI (dependencies): pgpass is a first-party sub-package of the node-postgres monorepo maintained by the same author (brianc). | ai | |
| dependencies | unvetted-dep:pg-pool | AI (dependencies): pg-pool is a first-party sub-package of the node-postgres monorepo maintained by the same author (brianc). | ai | |
| dependencies | unvetted-dep:pg-types | AI (dependencies): pg-types is a first-party sub-package of the node-postgres monorepo maintained by the same author (brianc). | ai | |
| dependencies | unvetted-dep:pg-protocol | AI (dependencies): pg-protocol is a first-party sub-package of the node-postgres monorepo maintained by the same author (brianc). | ai | |
| dependencies | unvetted-dep:pg-cloudflare | AI (dependencies): pg-cloudflare is a first-party optional sub-package of the node-postgres monorepo maintained by the same author (brianc). | ai | |
| dependencies | unvetted-dep:pg-connection-string | AI (dependencies): pg-connection-string is a first-party sub-package of the node-postgres monorepo maintained by the same author (brianc). | ai |
Versions (showing 12 of 12)
| Version | Deps | Published |
|---|---|---|
| 8.21.0 | 6 / 9 | |
| 8.20.0 | 6 / 9 | |
| 8.19.0 | 6 / 9 | |
| 8.18.0 | 6 / 9 | |
| 8.17.2 | 6 / 9 | |
| 8.17.1 | 6 / 9 | |
| 8.17.0 | 6 / 9 | |
| 8.16.3 | 6 / 9 | |
| 8.16.2 | 6 / 9 | |
| 8.16.1 | 6 / 9 | |
| 8.16.0 | 6 / 9 | |
| 8.15.6 | 6 / 10 |
v8.21.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.19.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.18.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.17.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.17.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.17.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.16.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.16.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.16.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.16.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.15.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.