@pgsql/traverse
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:pg-proto-parser | AI (phantom-deps): pg-proto-parser is a declared runtime dependency; phantom-dep heuristic fires because it's not directly imported in source but used via build scripts. | ai |
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 17.2.6 | 2 / 1 | |
| 17.2.5 | 2 / 1 | |
| 17.2.4 | 2 / 1 | |
| 17.2.3 | 2 / 1 | |
| 17.2.2 | 2 / 1 | |
| 17.2.1 | 2 / 1 | |
| 17.2.0 | 2 / 0 | |
| 17.1.0 | 2 / 0 |
v17.2.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v17.2.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v17.2.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v17.2.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v17.2.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v17.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v17.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v17.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.