@spark-ui/icons
spark-ui icons
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:cors | AI (typosquat): Scoped UI icon package from leboncoin/spark-web monorepo; no relation to cors. | ai |
Versions (showing 51 of 122)
| Version | Deps | Published |
|---|---|---|
| 18.0.5 | 0 / 5 | |
| 18.0.4 | 0 / 5 | |
| 18.0.3 | 0 / 5 | |
| 18.0.2 | 0 / 5 | |
| 18.0.1 | 0 / 5 | |
| 18.0.0 | 0 / 5 | |
| 17.16.0 | 0 / 5 | |
| 17.15.9 | 0 / 5 | |
| 17.15.8 | 0 / 5 | |
| 17.15.7 | 0 / 5 | |
| 17.15.6 | 0 / 5 | |
| 17.15.5 | 0 / 5 | |
| 17.15.4 | 0 / 5 | |
| 17.15.3 | 0 / 5 | |
| 17.15.2 | 0 / 5 | |
| 17.15.0 | 0 / 5 | |
| 17.14.4 | 0 / 5 | |
| 17.14.3 | 0 / 5 | |
| 17.14.2 | 0 / 5 | |
| 17.14.1 | 0 / 5 | |
| 17.14.0 | 0 / 5 | |
| 17.13.2 | 0 / 5 | |
| 17.13.1 | 0 / 5 | |
| 17.13.0 | 0 / 5 | |
| 17.12.0 | 0 / 5 | |
| 17.11.3 | 0 / 5 | |
| 17.11.2 | 0 / 5 | |
| 17.11.1 | 0 / 5 | |
| 17.11.0 | 0 / 5 | |
| 17.10.4 | 0 / 5 | |
| 17.10.3 | 0 / 5 | |
| 17.10.2 | 0 / 5 | |
| 17.10.1 | 0 / 5 | |
| 17.10.0 | 0 / 5 | |
| 17.9.3 | 0 / 5 | |
| 17.9.2 | 0 / 5 | |
| 17.9.1 | 0 / 5 | |
| 17.9.0 | 0 / 5 | |
| 17.8.0 | 0 / 5 | |
| 17.7.0 | 0 / 5 | |
| 17.6.1 | 0 / 5 | |
| 17.6.0 | 0 / 5 | |
| 17.5.7 | 0 / 5 | |
| 17.5.6 | 0 / 5 | |
| 17.5.5 | 0 / 5 | |
| 17.5.4 | 0 / 5 | |
| 17.5.3 | 0 / 5 | |
| 17.5.2 | 0 / 5 | |
| 17.5.1 | 0 / 5 | |
| 17.5.0 | 0 / 5 | |
| 17.4.2 | 0 / 5 |
v18.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v18.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v18.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v18.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v18.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v18.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.16.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.15.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.15.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.15.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.15.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.15.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.15.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.15.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.15.2
2 findingsThis version was published by a different npm account than previous versions on 2026-07-06. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.