postman-sandbox
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:uvm | AI (dependencies): uvm is a first-party Postman Labs dependency; stable for this package. | ai | |
| dependencies | unvetted-dep:postman-collection | AI (dependencies): postman-collection is a first-party Postman Labs dependency; stable for this package. | ai | |
| dependencies | unvetted-dep:teleport-javascript | AI (dependencies): teleport-javascript is a documented serialization dep used by postman-sandbox; stable for this package. | ai | |
| semgrep | semgrep:api-obfuscation-reflect | AI (semgrep): Reflect.get used in a Proxy trap inside a sandbox — expected pattern for this package. | ai | |
| semgrep | semgrep:new-function-constructor | AI (semgrep): new Function() used only for timer global feature detection; benign and stable for this sandbox package. | ai |
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 6.7.0 | 4 / 48 | |
| 6.6.1 | 4 / 48 | |
| 6.6.0 | 4 / 48 | |
| 6.5.0 | 4 / 48 | |
| 6.4.0 | 4 / 48 | |
| 6.3.0 | 4 / 48 | |
| 6.2.2 | 4 / 48 | |
| 6.2.1 | 4 / 48 |
v6.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.2.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.