openapi-to-postmanv2
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 |
|---|---|---|---|---|
| semgrep | semgrep:new-function-constructor | AI (semgrep): AJV validator compilation pattern in bundled ajv6faker.js; stable and expected for this package. | ai | |
| dependencies | unvetted-dep:postman-collection | AI (dependencies): First-party Postman Labs dependency; expected for this package. | ai | |
| dependencies | unvetted-dep:oas-resolver-browser | AI (dependencies): Pinned ecosystem dep for OAS resolution; stable for this package. | ai |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 6.3.0 | 18 / 20 | |
| 6.2.0 | 18 / 20 | |
| 6.1.0 | 18 / 20 | |
| 6.0.1 | 18 / 20 | |
| 6.0.0 | 18 / 20 | |
| 5.8.0 | 17 / 10 | |
| 5.7.0 | 17 / 10 | |
| 5.6.0 | 17 / 10 | |
| 5.5.0 | 17 / 10 |
v6.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.2.0
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 (ayush.shrivastav) than the most recent previously approved version (nishat.sayyed) on 2026-06-29, but ayush.shrivastav 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.