postman-collection
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 |
|---|---|---|---|---|
| maintainer-change | maintainer-added | AI (maintainer-change): Routine team maintainer rotation at established org with strong track record. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Routine team maintainer rotation, not a takeover indicator here. | ai | |
| dependencies | unvetted-dep:liquid-json | AI (dependencies): Long-standing dependency of postman-collection; no malicious signals. | ai | |
| 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:http-reasons | 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:postman-url-encoder | AI (dependencies): First-party Postman ecosystem dependency; stable and expected for this package. | ai |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 5.3.1 | 11 / 32 | |
| 5.3.0 | 11 / 32 | |
| 5.2.1 | 11 / 32 | |
| 5.2.0 | 11 / 32 | |
| 5.1.1 | 11 / 32 | |
| 5.1.0 | 11 / 32 | |
| 5.0.2 | 11 / 32 | |
| 5.0.1 | 11 / 32 | |
| 5.0.0 | 11 / 32 |
v5.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.