openapi
1
Versions
—
License
No
Install Scripts
Missing
Provenance
Supply chain provenance
Status for the latest visible version.
No SLSA provenance
npm registry signatures
gitHead linked
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
sergeysovaevgenyifedotov
Keywords
convertswaggerapijstypesopenapitypescript
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| semgrep | semgrep:child-process-import | AI (semgrep): CLI tool; execSync usage is expected for a code-generation CLI, not a supply-chain risk. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Preset-loader pattern; loads user-configured preset modules by name, stable across versions. | ai | |
| phantom-deps | phantom-dep:@types/jest | AI (phantom-deps): Type-only dev dependency loaded by Jest convention, not a runtime import. | ai | |
| phantom-deps | phantom-dep:object-hash | AI (phantom-deps): Referenced in config files only; not a runtime import risk. | ai |
Versions (showing 1 of 1)
| Version | Deps | Published |
|---|---|---|
| 1.0.1 | 9 / 9 |
v1.0.1
1 finding
LOW
No provenance attestation
provenance
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.