@odx/icons
A library of icon assets for ODX
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 | large-new-source-files | AI (source-diff): Icon asset library; large file counts reflect generated icon assets, not injected code. | ai | |
| typosquat | typosquat.levenshtein:cors | AI (typosquat): Scoped Drägerwerk AG icon library; name similarity to 'cors' is coincidental, not a squatting attempt. | ai |
Versions (showing 10 of 10)
| Version | Deps | Published |
|---|---|---|
| 4.11.0 | 1 / 1 | |
| 4.10.0 | 1 / 1 | |
| 4.9.1 | 1 / 1 | |
| 4.9.0 | 1 / 2 | |
| 4.8.2 | 1 / 2 | |
| 4.8.1 | 1 / 2 | |
| 4.8.0 | 1 / 2 | |
| 4.7.0 | 1 / 2 | |
| 4.0.0 | 1 / 2 | |
| 3.69.0 | 0 / 0 |
v4.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.8.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.8.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.8.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: kevin.wardenga.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.69.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.