@spectrum-icons/illustrations
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): Known implicit Babel runtime dependency; stable for this transpiled package. | ai | |
| phantom-deps | phantom-dep:@react-aria/utils | AI (phantom-deps): Config-referenced dependency; stable for this package's build setup. | ai |
Versions (showing 10 of 10)
| Version | Deps | Published |
|---|---|---|
| 3.7.1 | 1 / 3 | |
| 3.7.0 | 1 / 1 | |
| 3.6.29 | 3 / 1 | |
| 3.6.28 | 3 / 1 | |
| 3.6.27 | 3 / 1 | |
| 3.6.26 | 3 / 1 | |
| 3.6.25 | 3 / 1 | |
| 3.6.24 | 3 / 1 | |
| 3.6.23 | 3 / 1 | |
| 3.6.22 | 3 / 1 |
v3.7.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.6.29
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.6.28
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.6.27
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.6.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.6.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.