swagger-fluent
A fluent client for OpenAPI and Swagger
1
Versions
MIT
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
sbw
Keywords
swaggeropenapiclient
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:request | AI (dependencies): The `request` package is a well-known deprecated HTTP client; its use is consistent with swagger-fluent's purpose and poses no malicious risk. Stable false positive for this package. | ai | |
| provenance | no-provenance | AI (provenance): swagger-fluent has never published with provenance attestation; this is consistent across its 12 versions and is not a security concern for this package. | ai |
Versions (showing 1 of 1)
| Version | Deps | Published |
|---|---|---|
| 5.0.3 | 3 / 7 |
v5.0.3
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.