@spectrum-icons/color
Spectrum UI components in React
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@swc/helpers | AI (phantom-deps): @swc/helpers is a known implicit runtime dep for SWC-compiled packages; stable false positive for this package. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Icon sub-package in a large monorepo; sparse README and no keywords are expected and stable across versions. | ai |
Versions (showing 10 of 10)
| Version | Deps | Published |
|---|---|---|
| 3.6.1 | 2 / 3 | |
| 3.6.0 | 2 / 2 | |
| 3.5.29 | 3 / 2 | |
| 3.5.28 | 3 / 2 | |
| 3.5.27 | 3 / 2 | |
| 3.5.26 | 3 / 2 | |
| 3.5.25 | 3 / 2 | |
| 3.5.24 | 3 / 2 | |
| 3.5.23 | 3 / 2 | |
| 3.5.22 | 3 / 2 |
v3.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.5.29
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.5.28
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.5.27
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.5.26
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.5.25
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.5.24
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.5.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.5.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.