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, 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 |
|---|---|---|---|---|
| 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 10 of 10)
| Version | Deps | Published |
|---|---|---|
| 6.7.2 | 4 / 48 | |
| 6.7.1 | 4 / 48 | |
| 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.2
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (appurvamurawat) than the most recent previously approved version (codenirvana) on 2026-07-21, but appurvamurawat is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v6.7.1
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (appurvamurawat) than the most recent previously approved version (codenirvana) on 2026-07-21, but appurvamurawat is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.