@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 — 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 |
|---|---|---|---|---|
| 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 44 of 44)
| Version | Deps | Published |
|---|---|---|
| 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 |
v0.62.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.61.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.60.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.60.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.59.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.58.0
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.57.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.57.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.56.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.55.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.54.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.54.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.54.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.53.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.52.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.51.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.50.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.49.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.49.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.48.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.48.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.48.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.48.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.48.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.48.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.48.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.47.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.46.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.46.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.46.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.45.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.45.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.45.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.45.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.45.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.45.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.45.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.44.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.44.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.