openapi-enforcer
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
gi60s
Keywords
openapiswaggervalidateresponsebuildcomposeparseformatdeserializeserializerequest validationrequest parsingresponse validationresponse serializingutilityutilsplugable
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| semgrep | semgrep:base64-decode | AI (semgrep): Decodes user-supplied base64 strings as part of OpenAPI byte format validation — not a payload risk. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Loads internal ./enforcers/<name> modules; name is controlled by library internals, not user input. | ai | |
| semgrep | semgrep:new-function-constructor | AI (semgrep): Builds named constructor functions for OpenAPI schema types; name comes from internal enforcer definitions, not external input. | ai |
Versions (showing 1 of 1)
| Version | Deps | Published |
|---|---|---|
| 1.23.0 | 2 / 4 |
v1.23.0
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.