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 — 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 |
|---|---|---|---|---|
| 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 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 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.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.8.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.