@react-spectrum/overlays
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
Versions (showing 60 of 60)
| Version | Deps | Published |
|---|---|---|
| 5.10.1 | 2 / 2 | |
| 5.10.0 | 2 / 0 | |
| 5.9.3 | 9 / 1 | |
| 5.9.2 | 9 / 1 | |
| 5.9.1 | 9 / 1 | |
| 5.9.0 | 9 / 1 | |
| 5.8.2 | 9 / 1 | |
| 5.8.1 | 9 / 1 | |
| 5.8.0 | 9 / 1 | |
| 5.7.7 | 9 / 1 | |
| 5.7.6 | 9 / 1 | |
| 5.7.5 | 9 / 1 | |
| 5.7.4 | 9 / 1 | |
| 5.7.3 | 9 / 1 | |
| 5.7.2 | 9 / 1 | |
| 5.7.1 | 9 / 1 | |
| 5.7.0 | 9 / 1 | |
| 5.6.5 | 9 / 1 | |
| 5.6.4 | 9 / 1 | |
| 5.6.3 | 9 / 1 | |
| 5.6.2 | 9 / 1 | |
| 5.6.1 | 9 / 1 | |
| 5.6.0 | 9 / 1 | |
| 5.5.5 | 9 / 1 | |
| 5.5.4 | 9 / 1 | |
| 5.5.3 | 9 / 1 | |
| 5.5.2 | 9 / 1 | |
| 5.5.1 | 9 / 1 | |
| 5.5.0 | 9 / 1 | |
| 5.4.0 | 9 / 1 | |
| 5.3.0 | 9 / 1 | |
| 5.2.0 | 9 / 1 | |
| 5.1.1 | 8 / 1 | |
| 5.1.0 | 8 / 1 | |
| 5.0.0 | 8 / 1 | |
| 4.1.0 | 8 / 1 | |
| 4.0.0 | 8 / 1 | |
| 3.8.0 | 8 / 1 | |
| 3.7.1 | 8 / 1 | |
| 3.7.0 | 8 / 1 | |
| 3.6.1 | 8 / 1 | |
| 3.6.0 | 8 / 1 | |
| 3.5.0 | 8 / 1 | |
| 3.4.8 | 8 / 1 | |
| 3.4.7 | 8 / 1 | |
| 3.4.6 | 8 / 1 | |
| 3.4.5 | 8 / 1 | |
| 3.4.4 | 8 / 1 | |
| 3.4.3 | 8 / 1 | |
| 3.4.2 | 8 / 1 | |
| 3.4.1 | 8 / 1 | |
| 3.4.0 | 8 / 1 | |
| 3.3.0 | 8 / 1 | |
| 3.2.2 | 8 / 1 | |
| 3.2.1 | 8 / 1 | |
| 3.2.0 | 8 / 1 | |
| 3.1.0 | 8 / 1 | |
| 3.0.2 | 8 / 1 | |
| 3.0.1 | 8 / 1 | |
| 3.0.0 | 8 / 1 |
v5.10.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.9.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.9.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.9.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.9.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.8.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.8.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.8.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.7.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.7.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.7.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.7.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.7.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.7.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.7.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.6.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.6.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.6.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.6.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.6.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.5.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.5.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.5.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.5.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.5.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.