postman-collection
2
Versions
—
License
No
Install Scripts
Missing
Provenance
Supply chain provenance
Status for the latest visible version.
No SLSA provenance
npm registry signatures
gitHead linked
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
shamasiskamalaknncodenirvanaappurvamurawatkdevakumaran
Keywords
postmancollectionsdk
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 decoding is used for HTTP response stream handling — a core, documented feature of this SDK. | ai | |
| dependencies | unvetted-dep:postman-url-encoder | AI (dependencies): First-party Postman ecosystem dependency; stable and expected for this package. | ai | |
| dependencies | unvetted-dep:liquid-json | AI (dependencies): Long-standing dependency of postman-collection; no malicious signals. | ai | |
| dependencies | unvetted-dep:mime-format | AI (dependencies): Long-standing dependency of postman-collection; no malicious signals. | ai | |
| dependencies | unvetted-dep:http-reasons | AI (dependencies): Long-standing dependency of postman-collection; no malicious signals. | ai |
v5.1.1
1 finding
LOW
No provenance attestation
provenance
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.1.0
1 finding
LOW
No provenance attestation
provenance
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.