swagger-client
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 |
|---|---|---|---|---|
| publish-pattern | dormant-publish | AI (publish-pattern): Official swagger-api org package; long dormancy reflects development cycle, not account takeover. | ai | |
| phantom-deps | phantom-dep:@scarf/scarf | AI (phantom-deps): @scarf/scarf is a telemetry opt-out package referenced in config, not imported directly — expected pattern. | ai | |
| dependencies | unvetted-dep:@swagger-api/apidom-reference | AI (dependencies): First-party swagger-api dependency; stable pattern across versions. | ai | |
| dependencies | unvetted-dep:@swagger-api/apidom-json-pointer | AI (dependencies): First-party swagger-api dependency; stable pattern across versions. | ai | |
| dependencies | unvetted-dep:@swagger-api/apidom-ns-openapi-3-1 | AI (dependencies): First-party swagger-api dependency; stable pattern across versions. | ai | |
| dependencies | unvetted-dep:@swagger-api/apidom-core | AI (dependencies): First-party swagger-api dependency; stable pattern across versions. | ai | |
| dependencies | unvetted-dep:node-abort-controller | AI (dependencies): Standard AbortController polyfill for Node.js; well-known package used for browser compatibility. | ai | |
| provenance | no-provenance | AI (provenance): Established package predating Sigstore provenance adoption; absence is expected. | ai | |
| dependencies | unvetted-dep:node-fetch-commonjs | AI (dependencies): Standard fetch polyfill for Node.js; well-known package used for browser compatibility. | ai | |
| dependencies | unvetted-dep:@swagger-api/apidom-error | AI (dependencies): First-party swagger-api dependency; stable pattern across versions. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 3.37.4 | 18 / 36 | |
| 3.37.3 | 19 / 36 | |
| 3.37.2 | 19 / 36 | |
| 3.35.0 | 18 / 36 | |
| 3.26.7 | 15 / 35 |
v3.37.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.37.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.37.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.35.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.26.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.