pgpass
Module for reading .pgpass
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | obfuscated-file:coverage/prettify.js | AI (source-diff): Google prettify.js from nyc coverage output; standard minified vendor file, not obfuscation. | ai | |
| dependencies | unvetted-dep:split2 | AI (dependencies): split2 is a well-known, widely-used stream utility maintained by the Fastify team; its use in a .pgpass file parser is entirely appropriate and poses no real risk. | ai | |
| provenance | no-provenance | AI (provenance): pgpass is a long-established package (1584 days); lack of Sigstore provenance is common and not a risk signal for this package. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 1.0.6 | 0 / 9 | |
| 1.0.5 | 1 / 9 | |
| 1.0.4 | 1 / 9 | |
| 1.0.3 | 1 / 9 | |
| 1.0.2 | 1 / 9 | |
| 1.0.1 | 1 / 9 | |
| 1.0.0 | 1 / 9 |
v1.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.3
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.