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 51 of 121)
| Version | Deps | Published |
|---|---|---|
| 3.37.7 | 18 / 36 | |
| 3.37.6 | 18 / 36 | |
| 3.37.5 | 18 / 36 | |
| 3.37.4 | 18 / 36 | |
| 3.37.3 | 19 / 36 | |
| 3.37.2 | 19 / 36 | |
| 3.37.1 | 19 / 36 | |
| 3.37.0 | 19 / 36 | |
| 3.36.2 | 18 / 36 | |
| 3.36.1 | 18 / 36 | |
| 3.35.0 | 18 / 36 | |
| 3.34.4 | 18 / 36 | |
| 3.34.3 | 18 / 36 | |
| 3.34.2 | 18 / 36 | |
| 3.34.1 | 18 / 36 | |
| 3.34.0 | 18 / 36 | |
| 3.33.2 | 18 / 36 | |
| 3.33.1 | 18 / 36 | |
| 3.33.0 | 18 / 36 | |
| 3.32.4 | 18 / 36 | |
| 3.32.3 | 18 / 36 | |
| 3.32.2 | 18 / 36 | |
| 3.32.1 | 18 / 36 | |
| 3.32.0 | 18 / 36 | |
| 3.31.0 | 18 / 36 | |
| 3.30.1 | 18 / 36 | |
| 3.30.0 | 18 / 36 | |
| 3.29.4 | 17 / 36 | |
| 3.29.3 | 17 / 36 | |
| 3.29.2 | 16 / 36 | |
| 3.29.1 | 16 / 36 | |
| 3.29.0 | 17 / 36 | |
| 3.28.3 | 17 / 36 | |
| 3.28.2 | 17 / 36 | |
| 3.28.1 | 17 / 36 | |
| 3.28.0 | 17 / 36 | |
| 3.27.9 | 17 / 35 | |
| 3.27.8 | 17 / 35 | |
| 3.27.7 | 17 / 35 | |
| 3.27.6 | 17 / 35 | |
| 3.27.5 | 17 / 35 | |
| 3.27.4 | 16 / 35 | |
| 3.27.3 | 15 / 35 | |
| 3.27.2 | 15 / 35 | |
| 3.27.1 | 15 / 35 | |
| 3.27.0 | 15 / 35 | |
| 3.26.8 | 15 / 35 | |
| 3.26.7 | 15 / 35 | |
| 3.10.9 | 14 / 34 | |
| 3.10.8 | 18 / 44 | |
| 3.10.7 | 18 / 41 |
v3.37.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.37.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.37.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.37.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.36.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.36.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.34.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.34.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.34.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.34.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.34.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.33.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.33.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.33.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.32.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.32.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.32.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.32.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.32.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.31.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.30.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.30.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.29.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.29.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.29.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.29.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.29.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.28.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.28.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.28.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.28.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.27.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.27.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.27.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.27.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.27.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.27.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.27.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.27.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.27.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.27.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.26.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.10.9
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.10.8
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.10.7
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.