swagger-ui-dist
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
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): new Function() usage is in a minified bundle artifact (swagger-ui-es-bundle-core.js). Standard pattern in large JS bundles for template engines/parsers; not malicious for this package. | ai | |
| phantom-deps | phantom-dep:@scarf/scarf | AI (phantom-deps): @scarf/scarf is a telemetry package intentionally used via config files rather than direct imports; this is its documented usage pattern and is legitimate for swagger-ui-dist. | ai |
Versions (showing 100 of 119)
| Version | Deps | Published |
|---|---|---|
| 5.32.11 | 1 / 0 | |
| 5.32.10 | 1 / 0 | |
| 5.32.9 | 1 / 0 | |
| 5.32.8 | 1 / 0 | |
| 5.32.7 | 1 / 0 | |
| 5.32.6 | 1 / 0 | |
| 5.32.5 | 1 / 0 | |
| 5.32.4 | 1 / 0 | |
| 5.32.3 | 1 / 0 | |
| 5.32.2 | 1 / 0 | |
| 5.32.1 | 1 / 0 | |
| 5.32.0 | 1 / 0 | |
| 5.31.2 | 1 / 0 | |
| 5.31.1 | 1 / 0 | |
| 5.31.0 | 1 / 0 | |
| 5.30.3 | 1 / 0 | |
| 5.30.2 | 1 / 0 | |
| 5.30.1 | 1 / 0 | |
| 5.30.0 | 1 / 0 | |
| 5.29.5 | 1 / 0 | |
| 5.29.4 | 1 / 0 | |
| 5.29.3 | 1 / 0 | |
| 5.29.2 | 1 / 0 | |
| 5.29.1 | 1 / 0 | |
| 5.29.0 | 1 / 0 | |
| 5.28.1 | 1 / 0 | |
| 5.28.0 | 1 / 0 | |
| 5.27.1 | 1 / 0 | |
| 5.27.0 | 1 / 0 | |
| 5.26.2 | 1 / 0 | |
| 5.26.1 | 1 / 0 | |
| 5.26.0 | 1 / 0 | |
| 5.25.4 | 1 / 0 | |
| 5.25.3 | 1 / 0 | |
| 5.25.2 | 1 / 0 | |
| 5.24.2 | 1 / 0 | |
| 5.24.1 | 1 / 0 | |
| 5.24.0 | 1 / 0 | |
| 5.22.0 | 1 / 0 | |
| 5.21.0 | 1 / 0 | |
| 5.20.8 | 1 / 0 | |
| 5.20.7 | 1 / 0 | |
| 5.20.6 | 1 / 0 | |
| 5.20.5 | 1 / 0 | |
| 5.20.4 | 1 / 0 | |
| 5.20.3 | 1 / 0 | |
| 5.20.2 | 1 / 0 | |
| 5.20.1 | 1 / 0 | |
| 5.20.0 | 1 / 0 | |
| 5.19.0 | 1 / 0 | |
| 5.18.3 | 1 / 0 | |
| 5.18.2 | 1 / 0 | |
| 5.18.1 | 1 / 0 | |
| 5.18.0 | 1 / 0 | |
| 5.17.14 | 0 / 0 | |
| 5.17.13 | 0 / 0 | |
| 5.17.12 | 0 / 0 | |
| 5.17.10 | 0 / 0 | |
| 5.17.9 | 0 / 0 | |
| 5.17.8 | 0 / 0 | |
| 5.17.7 | 0 / 0 | |
| 5.17.6 | 0 / 0 | |
| 5.17.5 | 0 / 0 | |
| 5.17.4 | 0 / 0 | |
| 5.17.3 | 0 / 0 | |
| 5.17.2 | 0 / 0 | |
| 5.17.1 | 0 / 0 | |
| 5.17.0 | 0 / 0 | |
| 5.16.2 | 0 / 0 | |
| 5.16.1 | 0 / 0 | |
| 5.16.0 | 0 / 0 | |
| 5.15.2 | 0 / 0 | |
| 5.15.1 | 0 / 0 | |
| 5.15.0 | 0 / 0 | |
| 5.14.0 | 0 / 0 | |
| 5.13.0 | 0 / 0 | |
| 5.12.3 | 0 / 0 | |
| 5.12.2 | 0 / 0 | |
| 5.12.0 | 0 / 0 | |
| 5.11.10 | 0 / 0 | |
| 5.11.9 | 0 / 0 | |
| 5.11.8 | 0 / 0 | |
| 5.11.7 | 0 / 0 | |
| 5.11.6 | 0 / 0 | |
| 5.11.5 | 0 / 0 | |
| 5.11.4 | 0 / 0 | |
| 5.11.3 | 0 / 0 | |
| 5.11.2 | 0 / 0 | |
| 5.11.1 | 0 / 0 | |
| 5.11.0 | 0 / 0 | |
| 5.10.5 | 0 / 0 | |
| 5.10.4 | 0 / 0 | |
| 5.10.3 | 0 / 0 | |
| 5.10.2 | 0 / 0 | |
| 5.10.0 | 0 / 0 | |
| 5.9.4 | 0 / 0 | |
| 5.9.3 | 0 / 0 | |
| 5.9.2 | 0 / 0 | |
| 5.9.1 | 0 / 0 | |
| 5.9.0 | 0 / 0 |
v5.32.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.32.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.32.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.21.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.20.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.20.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.20.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.20.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.20.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.20.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.20.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.20.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.20.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.19.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.18.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.18.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.18.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.18.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.17.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.17.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.17.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.17.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.17.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.17.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.17.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.17.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.17.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.17.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.17.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.17.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.17.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.17.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.16.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.16.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.16.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.15.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.15.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.15.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.14.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.13.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.12.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.12.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.12.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.11.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.11.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.11.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.11.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.11.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.11.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.11.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.11.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.11.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.11.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.11.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.10.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.10.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.10.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.10.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.10.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.9.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.9.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.9.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.9.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.9.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.