pg-promise
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:spex | AI (dependencies): spex is a companion library by the same author (vitaly-t); stable dependency across many pg-promise versions. | ai | |
| dependencies | unvetted-dep:assert-options | AI (dependencies): assert-options is a companion library by the same author (vitaly-t); stable dependency across many pg-promise versions. | ai |
Versions (showing 12 of 12)
| Version | Deps | Published |
|---|---|---|
| 12.6.2 | 4 / 11 | |
| 12.6.1 | 4 / 11 | |
| 12.6.0 | 4 / 11 | |
| 12.5.0 | 4 / 11 | |
| 12.4.0 | 4 / 11 | |
| 12.3.0 | 4 / 11 | |
| 12.2.0 | 4 / 11 | |
| 12.1.3 | 4 / 11 | |
| 12.1.2 | 4 / 11 | |
| 12.1.1 | 4 / 11 | |
| 12.1.0 | 4 / 12 | |
| 12.0.0 | 4 / 12 |
v12.6.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v12.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v12.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v12.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v12.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.