@react-spectrum/actiongroup
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:@babel/runtime | AI (phantom-deps): Framework-scoped runtime dependency; standard pattern for React libraries in this ecosystem. | ai | |
| phantom-deps | phantom-dep:@react-aria/focus | AI (phantom-deps): React Spectrum monorepo convention; @react-aria packages loaded by framework pattern. | ai | |
| phantom-deps | phantom-dep:@react-aria/button | AI (phantom-deps): React Spectrum monorepo convention; @react-aria packages loaded by framework pattern. | ai | |
| phantom-deps | phantom-dep:@react-types/button | AI (phantom-deps): React Spectrum monorepo convention; @react-types packages loaded by framework pattern. | ai | |
| phantom-deps | phantom-dep:@react-spectrum/form | AI (phantom-deps): Same-org scoped package within React Spectrum monorepo; stable pattern. | ai | |
| phantom-deps | phantom-dep:@react-aria/selection | AI (phantom-deps): React Spectrum monorepo convention; @react-aria packages loaded by framework pattern. | ai |
Versions (showing 51 of 208)
| Version | Deps | Published |
|---|---|---|
| 3.12.1 | 3 / 2 | |
| 3.12.0 | 3 / 0 | |
| 3.11.7 | 17 / 1 | |
| 3.11.6 | 17 / 1 | |
| 3.11.5 | 17 / 1 | |
| 3.11.4 | 17 / 1 | |
| 3.11.3 | 17 / 1 | |
| 3.11.2 | 17 / 1 | |
| 3.11.1 | 17 / 1 | |
| 3.11.0 | 17 / 1 | |
| 3.10.17 | 16 / 1 | |
| 3.10.16 | 16 / 1 | |
| 3.10.15 | 16 / 1 | |
| 3.10.14 | 16 / 1 | |
| 3.10.13 | 16 / 1 | |
| 3.10.12 | 16 / 1 | |
| 3.10.11 | 16 / 1 | |
| 3.10.10 | 16 / 1 | |
| 3.10.9 | 16 / 1 | |
| 3.10.8 | 16 / 1 | |
| 3.10.7 | 16 / 1 | |
| 3.10.6 | 16 / 1 | |
| 3.10.5 | 16 / 1 | |
| 3.10.4 | 16 / 1 | |
| 3.10.3 | 16 / 1 | |
| 3.10.2 | 16 / 1 | |
| 3.10.1 | 16 / 1 | |
| 3.10.0 | 16 / 1 | |
| 3.9.4 | 20 / 1 | |
| 3.9.3 | 20 / 1 | |
| 3.9.2 | 20 / 1 | |
| 3.9.1 | 20 / 1 | |
| 3.9.0 | 20 / 1 | |
| 3.8.3 | 20 / 1 | |
| 3.8.2 | 20 / 1 | |
| 3.8.1 | 20 / 1 | |
| 3.8.0 | 20 / 1 | |
| 3.7.3 | 20 / 1 | |
| 3.7.2 | 20 / 1 | |
| 3.7.1 | 20 / 1 | |
| 3.7.0 | 20 / 1 | |
| 3.6.1 | 20 / 1 | |
| 3.6.0 | 20 / 1 | |
| 3.5.1 | 20 / 1 | |
| 3.5.0 | 20 / 1 | |
| 3.4.4 | 20 / 1 | |
| 3.4.3 | 20 / 1 | |
| 3.4.2 | 20 / 1 | |
| 3.4.1 | 20 / 1 | |
| 3.4.0 | 20 / 1 | |
| 3.3.1 | 20 / 1 |
v3.12.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.11.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.11.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.11.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.11.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.11.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.11.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.11.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.11.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.10.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.10.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.10.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.10.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.10.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.10.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.10.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.10.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.10.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.10.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.10.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.10.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.10.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.10.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.10.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.10.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.10.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.10.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.9.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.9.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.9.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.9.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.9.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.8.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.8.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.8.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.8.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.7.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.7.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.7.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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.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.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.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.4.3
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.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.