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, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:@kyleshockey/js-yaml | AI (dependencies): Fork by listed project contributor, used as direct js-yaml replacement. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): Dep swap matches known contributor's fork, benign for this trusted publisher. | ai | |
| semgrep | semgrep:new-function-constructor | AI (semgrep): new Function inside bundled JSON-patch/parser deps; stable build pattern. | ai | |
| source-diff | source-size-tripled | AI (source-diff): Size growth is the added UMD bundle output, expected for this package. | ai | |
| source-diff | net-exec-file:browser/index.js | AI (source-diff): Network+eval co-occurrence is bundled fetch/parser code in the UMD build; no dropper behavior. | ai | |
| source-diff | obfuscated-file:browser/index.js | AI (source-diff): browser/index.js is the published webpack UMD bundle; minified build output, not obfuscation. | ai | |
| dependencies | unvetted-dep:node-inspector | AI (dependencies): Legit optional dev-debug dependency, not runtime-loaded malicious code. | ai | |
| phantom-deps | phantom-dep:node-inspector | AI (phantom-deps): Used via npm script 'inspector', not imported in source; expected pattern. | 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 | |
| publish-pattern | dormant-publish | AI (publish-pattern): Official swagger-api org package; long dormancy reflects development cycle, not account takeover. | ai | |
| dependencies | unvetted-dep:@swagger-api/apidom-core | AI (dependencies): First-party swagger-api dependency; stable pattern across versions. | ai | |
| provenance | no-provenance | AI (provenance): Established package predating Sigstore provenance adoption; absence is expected. | ai | |
| dependencies | unvetted-dep:node-abort-controller | AI (dependencies): Standard AbortController polyfill for Node.js; well-known package used for browser compatibility. | 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-ns-openapi-3-1 | 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-reference | AI (dependencies): First-party swagger-api dependency; stable pattern across versions. | ai | |
| dependencies | unvetted-dep:@swagger-api/apidom-error | AI (dependencies): First-party swagger-api dependency; stable pattern across versions. | ai |
Versions (showing 21 of 121)
| Version | Deps | Published |
|---|---|---|
| 3.1.2 | 10 / 22 | |
| 3.1.1 | 10 / 22 | |
| 3.1.0 | 10 / 22 | |
| 3.0.20 | 10 / 21 | |
| 3.0.19 | 10 / 21 | |
| 3.0.18 | 10 / 21 | |
| 3.0.17 | 10 / 21 | |
| 3.0.16 | 10 / 21 | |
| 3.0.15 | 10 / 21 | |
| 3.0.14 | 10 / 21 | |
| 3.0.13 | 10 / 21 | |
| 3.0.12 | 10 / 21 | |
| 3.0.11 | 10 / 21 | |
| 3.0.10 | 10 / 21 | |
| 3.0.9 | 10 / 21 | |
| 3.0.8 | 10 / 21 | |
| 3.0.7 | 10 / 21 | |
| 3.0.6 | 10 / 21 | |
| 3.0.5 | 11 / 21 | |
| 3.0.2 | 11 / 21 | |
| 3.0.1 | 11 / 21 |
v3.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.20
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.19
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.18
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.