@baseline-ui/icons
A collection of icons for the baseline-ui library
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 |
|---|---|---|---|---|
| source-diff | obfuscated-file:36/index.js | AI (source-diff): Minified icon bundle; content is readable SVG React components, not obfuscated malware. | ai | |
| source-diff | obfuscated-file:36/index.mjs | AI (source-diff): ESM variant of the same minified icon bundle; same reasoning applies. | ai | |
| typosquat | typosquat.levenshtein:cors | AI (typosquat): Scoped package @baseline-ui/icons is a legitimate PSPDFKit icon library; Levenshtein match against 'cors' is a false positive with no brand impersonation intent. | ai | |
| phantom-deps | phantom-dep:dompurify | AI (phantom-deps): dompurify is a declared runtime dependency for SVG sanitization; static analysis not finding a direct import is expected for this type of icon library. | ai |
Versions (showing 100 of 125)
| Version | Deps | Published |
|---|---|---|
| 1.2.0 | 0 / 4 | |
| 1.1.0 | 0 / 4 | |
| 1.0.0 | 0 / 4 | |
| 0.63.0 | 0 / 4 | |
| 0.62.0 | 0 / 4 | |
| 0.61.0 | 1 / 3 | |
| 0.60.1 | 1 / 3 | |
| 0.60.0 | 1 / 3 | |
| 0.59.0 | 1 / 3 | |
| 0.58.0 | 1 / 3 | |
| 0.57.2 | 1 / 3 | |
| 0.57.1 | 1 / 3 | |
| 0.57.0 | 1 / 3 | |
| 0.56.0 | 1 / 3 | |
| 0.55.0 | 1 / 3 | |
| 0.54.2 | 1 / 3 | |
| 0.54.1 | 1 / 3 | |
| 0.54.0 | 1 / 3 | |
| 0.53.0 | 1 / 3 | |
| 0.52.0 | 1 / 3 | |
| 0.51.0 | 1 / 3 | |
| 0.50.0 | 1 / 3 | |
| 0.49.1 | 1 / 3 | |
| 0.49.0 | 1 / 3 | |
| 0.48.6 | 1 / 3 | |
| 0.48.5 | 1 / 3 | |
| 0.48.4 | 1 / 3 | |
| 0.48.3 | 1 / 3 | |
| 0.48.2 | 1 / 3 | |
| 0.48.1 | 1 / 3 | |
| 0.48.0 | 1 / 3 | |
| 0.47.0 | 1 / 3 | |
| 0.46.2 | 1 / 3 | |
| 0.46.1 | 1 / 3 | |
| 0.46.0 | 1 / 3 | |
| 0.45.8 | 1 / 3 | |
| 0.45.7 | 1 / 3 | |
| 0.45.6 | 1 / 3 | |
| 0.45.5 | 1 / 3 | |
| 0.45.4 | 1 / 3 | |
| 0.45.3 | 1 / 3 | |
| 0.45.2 | 1 / 3 | |
| 0.45.1 | 1 / 3 | |
| 0.45.0 | 1 / 3 | |
| 0.44.2 | 1 / 3 | |
| 0.44.1 | 1 / 3 | |
| 0.44.0 | 1 / 3 | |
| 0.43.0 | 1 / 3 | |
| 0.42.0 | 1 / 3 | |
| 0.41.1 | 4 / 3 | |
| 0.41.0 | 4 / 3 | |
| 0.40.1 | 4 / 3 | |
| 0.40.0 | 4 / 3 | |
| 0.39.1 | 4 / 3 | |
| 0.39.0 | 4 / 3 | |
| 0.38.0 | 4 / 3 | |
| 0.37.1 | 4 / 3 | |
| 0.37.0 | 4 / 3 | |
| 0.36.0 | 4 / 3 | |
| 0.35.1 | 4 / 3 | |
| 0.35.0 | 4 / 3 | |
| 0.34.0 | 4 / 3 | |
| 0.33.1 | 4 / 3 | |
| 0.33.0 | 4 / 3 | |
| 0.32.0 | 4 / 3 | |
| 0.31.1 | 4 / 3 | |
| 0.31.0 | 4 / 3 | |
| 0.30.0 | 4 / 3 | |
| 0.29.3 | 4 / 3 | |
| 0.29.2 | 4 / 3 | |
| 0.29.1 | 4 / 3 | |
| 0.29.0 | 4 / 3 | |
| 0.28.0 | 4 / 3 | |
| 0.27.0 | 4 / 3 | |
| 0.26.0 | 4 / 3 | |
| 0.25.0 | 4 / 3 | |
| 0.24.1 | 4 / 3 | |
| 0.24.0 | 4 / 3 | |
| 0.23.0 | 4 / 3 | |
| 0.22.1 | 4 / 3 | |
| 0.22.0 | 4 / 3 | |
| 0.21.0 | 4 / 3 | |
| 0.20.1 | 4 / 3 | |
| 0.20.0 | 4 / 3 | |
| 0.19.7 | 4 / 3 | |
| 0.19.6 | 4 / 3 | |
| 0.19.5 | 4 / 3 | |
| 0.19.4 | 4 / 3 | |
| 0.19.3 | 4 / 3 | |
| 0.19.2 | 4 / 3 | |
| 0.19.1 | 4 / 3 | |
| 0.19.0 | 4 / 3 | |
| 0.18.1 | 4 / 3 | |
| 0.18.0 | 4 / 3 | |
| 0.17.0 | 4 / 3 | |
| 0.16.0 | 4 / 3 | |
| 0.15.0 | 4 / 3 | |
| 0.14.0 | 4 / 3 | |
| 0.13.0 | 4 / 3 | |
| 0.12.0 | 4 / 3 |
v1.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.42.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.41.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.41.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.40.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.40.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.39.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.39.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.38.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.37.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.37.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.36.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.35.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.35.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.34.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.33.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.33.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.32.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.31.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.31.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.30.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.29.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.29.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.29.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.29.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.28.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.27.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.26.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.25.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.24.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.24.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.23.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.22.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.22.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.21.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.20.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.20.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.18.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.18.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.15.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.14.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.