@react-spectrum/menu
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 Babel runtime loaded by convention in transpiled packages; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:@react-stately/utils | AI (phantom-deps): React Spectrum monorepo dependency referenced in config; expected for component libraries in this ecosystem. | ai | |
| phantom-deps | phantom-dep:@react-aria/selection | AI (phantom-deps): React Spectrum monorepo dependency referenced in config; expected for component libraries in this ecosystem. | ai | |
| phantom-deps | phantom-dep:@react-aria/virtualizer | AI (phantom-deps): React Spectrum monorepo dependency referenced in config; expected for component libraries in this ecosystem. | ai | |
| phantom-deps | phantom-dep:@react-spectrum/divider | AI (phantom-deps): Same-org scoped dependency; component composition is expected in Spectrum library. | ai | |
| phantom-deps | phantom-dep:@react-spectrum/checkbox | AI (phantom-deps): Same-org scoped dependency; component composition is expected in Spectrum library. | ai | |
| phantom-deps | phantom-dep:@swc/helpers | AI (phantom-deps): @swc/helpers is a known implicit runtime dependency of SWC-compiled code; stable for this package. | ai | |
| phantom-deps | phantom-dep:@react-aria/overlays | AI (phantom-deps): Transitive dependency referenced in config; expected for React Spectrum menu component. | ai | |
| phantom-deps | phantom-dep:@react-stately/overlays | AI (phantom-deps): Transitive dependency referenced in config; expected for React Spectrum menu component. | ai |
Versions (showing 64 of 64)
| Version | Deps | Published |
|---|---|---|
| 3.23.1 | 3 / 2 | |
| 3.23.0 | 3 / 0 | |
| 3.22.11 | 22 / 1 | |
| 3.22.10 | 22 / 1 | |
| 3.22.9 | 22 / 1 | |
| 3.22.8 | 22 / 1 | |
| 3.22.7 | 22 / 1 | |
| 3.22.6 | 22 / 1 | |
| 3.22.5 | 22 / 1 | |
| 3.22.4 | 22 / 1 | |
| 3.22.3 | 22 / 1 | |
| 3.22.2 | 22 / 1 | |
| 3.22.1 | 22 / 1 | |
| 3.22.0 | 22 / 1 | |
| 3.21.3 | 22 / 1 | |
| 3.21.2 | 22 / 1 | |
| 3.21.1 | 22 / 1 | |
| 3.21.0 | 22 / 1 | |
| 3.20.5 | 22 / 1 | |
| 3.20.4 | 22 / 1 | |
| 3.20.3 | 22 / 1 | |
| 3.20.2 | 22 / 1 | |
| 3.20.1 | 22 / 1 | |
| 3.20.0 | 22 / 1 | |
| 3.19.1 | 22 / 1 | |
| 3.19.0 | 22 / 1 | |
| 3.18.1 | 22 / 1 | |
| 3.18.0 | 22 / 1 | |
| 3.17.0 | 22 / 1 | |
| 3.16.0 | 22 / 1 | |
| 3.15.1 | 27 / 1 | |
| 3.15.0 | 27 / 1 | |
| 3.14.0 | 27 / 1 | |
| 3.13.0 | 27 / 1 | |
| 3.12.0 | 27 / 1 | |
| 3.11.1 | 26 / 1 | |
| 3.11.0 | 26 / 1 | |
| 3.10.1 | 26 / 1 | |
| 3.10.0 | 26 / 1 | |
| 3.9.2 | 26 / 1 | |
| 3.9.1 | 26 / 1 | |
| 3.9.0 | 26 / 1 | |
| 3.8.2 | 26 / 1 | |
| 3.8.1 | 26 / 1 | |
| 3.8.0 | 26 / 1 | |
| 3.7.1 | 26 / 1 | |
| 3.7.0 | 26 / 1 | |
| 3.6.4 | 26 / 1 | |
| 3.6.3 | 26 / 1 | |
| 3.6.2 | 26 / 1 | |
| 3.6.1 | 26 / 1 | |
| 3.6.0 | 26 / 1 | |
| 3.5.1 | 26 / 1 | |
| 3.5.0 | 26 / 1 | |
| 3.4.0 | 26 / 1 | |
| 3.3.0 | 23 / 1 | |
| 3.2.3 | 23 / 1 | |
| 3.2.2 | 23 / 1 | |
| 3.2.1 | 23 / 1 | |
| 3.2.0 | 23 / 1 | |
| 3.1.0 | 23 / 1 | |
| 3.0.2 | 23 / 1 | |
| 3.0.1 | 23 / 1 | |
| 3.0.0 | 23 / 1 |
v3.23.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.23.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.22.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.22.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.22.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.22.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.22.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.22.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.22.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.22.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.22.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.22.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.22.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.22.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.21.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.21.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.21.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.21.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.20.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.20.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.20.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.20.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.20.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.20.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.19.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.19.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.18.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.18.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.17.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.16.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.15.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.15.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.14.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.13.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.12.0
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.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.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.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.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.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.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.0
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.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.