@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 25 of 125)
| Version | Deps | Published |
|---|---|---|
| 0.11.0 | 4 / 3 | |
| 0.10.0 | 4 / 3 | |
| 0.9.0 | 4 / 3 | |
| 0.8.5 | 4 / 3 | |
| 0.8.4 | 4 / 3 | |
| 0.8.3 | 4 / 3 | |
| 0.8.2 | 4 / 3 | |
| 0.8.1 | 4 / 3 | |
| 0.8.0 | 4 / 3 | |
| 0.7.3 | 4 / 3 | |
| 0.7.2 | 4 / 3 | |
| 0.7.1 | 4 / 3 | |
| 0.7.0 | 4 / 3 | |
| 0.6.2 | 4 / 3 | |
| 0.6.1 | 4 / 3 | |
| 0.6.0 | 4 / 3 | |
| 0.5.1 | 4 / 3 | |
| 0.5.0 | 4 / 3 | |
| 0.4.0 | 4 / 3 | |
| 0.3.0 | 4 / 3 | |
| 0.2.0 | 4 / 3 | |
| 0.1.3 | 3 / 3 | |
| 0.1.2 | 3 / 3 | |
| 0.1.1 | 3 / 3 | |
| 0.1.0 | 3 / 3 |
v0.11.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.