@spectrum-icons/ui
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 |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:uuid | AI (typosquat): @spectrum-icons/ui is a legitimate Adobe React Spectrum scoped package; Levenshtein match on short unscoped name 'ui' vs 'uuid' is a false positive. | ai | |
| typosquat | typosquat.levenshtein:pg | AI (typosquat): @spectrum-icons/ui is a legitimate Adobe React Spectrum scoped package; Levenshtein match on 'ui' vs 'pg' is a false positive. | ai | |
| typosquat | typosquat.levenshtein:qs | AI (typosquat): @spectrum-icons/ui is a legitimate Adobe React Spectrum scoped package; Levenshtein match on 'ui' vs 'qs' is a false positive. | ai | |
| typosquat | typosquat.levenshtein:joi | AI (typosquat): @spectrum-icons/ui is a legitimate Adobe React Spectrum scoped package; Levenshtein match on 'ui' vs 'joi' is a false positive. | ai | |
| typosquat | typosquat.levenshtein:yup | AI (typosquat): @spectrum-icons/ui is a legitimate Adobe React Spectrum scoped package; Levenshtein match on 'ui' vs 'yup' is a false positive. | ai | |
| phantom-deps | phantom-dep:@swc/helpers | AI (phantom-deps): @swc/helpers is a known implicit runtime dependency for SWC/Babel-compiled packages; stable pattern for this monorepo package. | ai |
Versions (showing 50 of 50)
| Version | Deps | Published |
|---|---|---|
| 3.7.1 | 3 / 3 | |
| 3.7.0 | 3 / 2 | |
| 3.6.23 | 4 / 2 | |
| 3.6.22 | 4 / 2 | |
| 3.6.21 | 4 / 2 | |
| 3.6.20 | 4 / 2 | |
| 3.6.19 | 3 / 2 | |
| 3.6.18 | 3 / 2 | |
| 3.6.17 | 3 / 2 | |
| 3.6.16 | 3 / 2 | |
| 3.6.15 | 3 / 2 | |
| 3.6.14 | 3 / 2 | |
| 3.6.13 | 3 / 2 | |
| 3.6.12 | 3 / 2 | |
| 3.6.11 | 3 / 2 | |
| 3.6.10 | 3 / 2 | |
| 3.6.9 | 3 / 1 | |
| 3.6.8 | 3 / 1 | |
| 3.6.7 | 3 / 1 | |
| 3.6.6 | 3 / 1 | |
| 3.6.5 | 3 / 1 | |
| 3.6.4 | 3 / 1 | |
| 3.6.3 | 3 / 1 | |
| 3.6.2 | 3 / 1 | |
| 3.6.1 | 3 / 1 | |
| 3.6.0 | 3 / 1 | |
| 3.5.5 | 3 / 1 | |
| 3.5.4 | 3 / 1 | |
| 3.5.3 | 3 / 1 | |
| 3.5.2 | 3 / 1 | |
| 3.5.1 | 3 / 1 | |
| 3.5.0 | 3 / 1 | |
| 3.4.2 | 3 / 1 | |
| 3.4.1 | 3 / 1 | |
| 3.4.0 | 3 / 1 | |
| 3.3.3 | 3 / 1 | |
| 3.3.2 | 3 / 1 | |
| 3.3.1 | 3 / 1 | |
| 3.3.0 | 3 / 1 | |
| 3.2.6 | 2 / 1 | |
| 3.2.5 | 2 / 1 | |
| 3.2.4 | 2 / 1 | |
| 3.2.3 | 2 / 1 | |
| 3.2.2 | 2 / 1 | |
| 3.2.1 | 2 / 1 | |
| 3.2.0 | 2 / 1 | |
| 3.1.0 | 2 / 2 | |
| 3.0.2 | 2 / 2 | |
| 3.0.1 | 2 / 2 | |
| 3.0.0 | 2 / 2 |
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. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.6.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.6.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.6.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.6.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.6.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.6.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.6.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.6.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.6.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.6.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.6.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.6.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.6.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.6.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.6.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.6.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.6.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.6.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.6.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.6.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.6.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.5.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.5.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.5.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.5.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.4.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.4.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.