swagger-ui-react
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| semgrep | semgrep:new-function-constructor | AI (semgrep): Fires in bundled output of a complex UI library; standard pattern in template/parser code within webpack bundles. | ai | |
| phantom-deps | phantom-dep:ieee754 | AI (phantom-deps): Bundled dependency declared in package.json but inlined in the bundle; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:base64-js | AI (phantom-deps): Bundled dependency declared in package.json but inlined in the bundle; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@scarf/scarf | AI (phantom-deps): Analytics dep referenced in config; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:react-inspector | AI (phantom-deps): Bundled dependency inlined in the bundle; stable false positive for this package. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 5.32.6 | 34 / 0 | |
| 5.32.5 | 34 / 0 | |
| 5.32.4 | 34 / 0 | |
| 5.32.3 | 34 / 0 | |
| 5.32.2 | 34 / 0 |
v5.32.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.32.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.32.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.32.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.