@react-stately/select
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:@react-types/shared | AI (phantom-deps): Declared dependency used transitively in React Spectrum monorepo; not a missing import issue. | ai | |
| phantom-deps | phantom-dep:@react-stately/utils | AI (phantom-deps): Declared dependency used transitively in React Spectrum monorepo; not a missing import issue. | ai | |
| phantom-deps | phantom-dep:@react-stately/selection | AI (phantom-deps): Declared dependency used transitively in React Spectrum monorepo; not a missing import issue. | ai | |
| phantom-deps | phantom-dep:@react-stately/collections | AI (phantom-deps): Declared dependency used transitively in React Spectrum monorepo; not a missing import issue. | ai |
Versions (showing 48 of 48)
| Version | Deps | Published |
|---|---|---|
| 3.10.1 | 2 / 2 | |
| 3.10.0 | 2 / 0 | |
| 3.9.2 | 7 / 0 | |
| 3.9.1 | 7 / 0 | |
| 3.9.0 | 7 / 0 | |
| 3.8.0 | 7 / 0 | |
| 3.7.1 | 6 / 0 | |
| 3.7.0 | 6 / 0 | |
| 3.6.14 | 6 / 0 | |
| 3.6.13 | 6 / 0 | |
| 3.6.12 | 6 / 0 | |
| 3.6.11 | 6 / 0 | |
| 3.6.10 | 6 / 0 | |
| 3.6.9 | 6 / 0 | |
| 3.6.8 | 6 / 0 | |
| 3.6.7 | 6 / 0 | |
| 3.6.6 | 6 / 0 | |
| 3.6.5 | 6 / 0 | |
| 3.6.4 | 6 / 0 | |
| 3.6.3 | 6 / 0 | |
| 3.6.2 | 6 / 0 | |
| 3.6.1 | 6 / 0 | |
| 3.6.0 | 6 / 0 | |
| 3.5.5 | 8 / 0 | |
| 3.5.4 | 8 / 0 | |
| 3.5.3 | 8 / 0 | |
| 3.5.2 | 8 / 0 | |
| 3.5.1 | 8 / 0 | |
| 3.5.0 | 8 / 0 | |
| 3.4.0 | 8 / 0 | |
| 3.3.4 | 8 / 0 | |
| 3.3.3 | 8 / 0 | |
| 3.3.2 | 8 / 0 | |
| 3.3.1 | 8 / 0 | |
| 3.3.0 | 8 / 0 | |
| 3.2.1 | 8 / 0 | |
| 3.2.0 | 8 / 0 | |
| 3.1.7 | 8 / 0 | |
| 3.1.6 | 8 / 0 | |
| 3.1.5 | 8 / 0 | |
| 3.1.4 | 8 / 0 | |
| 3.1.3 | 8 / 0 | |
| 3.1.2 | 8 / 0 | |
| 3.1.1 | 8 / 0 | |
| 3.1.0 | 8 / 0 | |
| 3.0.2 | 8 / 0 | |
| 3.0.1 | 8 / 0 | |
| 3.0.0 | 8 / 0 |
v3.10.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.9.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.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.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.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.4
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.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.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.1
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.