← Home

swagger-ui

npm Repository Homepage
5
Versions
—
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

swagger-apifehguykyleshockey

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
phantom-deps phantom-dep:@scarf/scarf AI (phantom-deps): Scarf telemetry declared as dep but loaded via config, not direct import; intentional pattern. ai
install-scripts install-script:postinstall AI (install-scripts): patch-package postinstall is a documented, stable pattern in swagger-ui across versions. ai
phantom-deps phantom-dep:patch-package AI (phantom-deps): patch-package is referenced in postinstall script; phantom-dep heuristic is a false positive here. ai
phantom-deps phantom-dep:ieee754 AI (phantom-deps): Declared for bundler/config use; stable false positive for this package. ai
phantom-deps phantom-dep:base64-js AI (phantom-deps): Declared for bundler/config use; stable false positive for this package. ai
phantom-deps phantom-dep:react-inspector AI (phantom-deps): Declared for bundler/config use; stable false positive for this package. ai

Versions (showing 5 of 5)

Version Deps Published
5.32.5 36 / 88
5.32.4 36 / 88
5.32.3 36 / 88
5.32.2 36 / 88
5.7.2 36 / 82

v5.32.5

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.

v5.32.4

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v5.32.3

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v5.32.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v5.7.2

2 findings
HIGH Package has 'postinstall' script install-scripts

Script: patch-package

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.