react-aria-components
A library of styleable components built using React Aria
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:@swc/helpers | AI (phantom-deps): @swc/helpers is a known implicit runtime dependency for SWC-compiled code; stable for this package. | ai | |
| phantom-deps | phantom-dep:@react-aria/accordion | AI (phantom-deps): Declared in package.json and referenced in config; normal pattern for monorepo-style re-exports. | ai | |
| phantom-deps | phantom-dep:use-sync-external-store | AI (phantom-deps): Declared in package.json and referenced in config; normal pattern for monorepo-style re-exports. | ai |
Versions (showing 34 of 34)
| Version | Deps | Published |
|---|---|---|
| 1.18.0 | 6 / 3 | |
| 1.17.0 | 6 / 1 | |
| 1.16.0 | 29 / 1 | |
| 1.15.1 | 29 / 1 | |
| 1.15.0 | 29 / 1 | |
| 1.14.0 | 29 / 1 | |
| 1.13.0 | 29 / 1 | |
| 1.12.2 | 29 / 1 | |
| 1.12.1 | 29 / 1 | |
| 1.12.0 | 29 / 1 | |
| 1.11.0 | 28 / 1 | |
| 1.10.1 | 28 / 1 | |
| 1.10.0 | 28 / 1 | |
| 1.9.0 | 28 / 1 | |
| 1.8.0 | 28 / 1 | |
| 1.7.1 | 26 / 1 | |
| 1.7.0 | 26 / 1 | |
| 1.6.0 | 34 / 0 | |
| 1.5.0 | 32 / 0 | |
| 1.4.1 | 32 / 0 | |
| 1.4.0 | 32 / 0 | |
| 1.3.3 | 28 / 0 | |
| 1.3.2 | 28 / 0 | |
| 1.3.1 | 28 / 0 | |
| 1.3.0 | 28 / 0 | |
| 1.2.1 | 23 / 0 | |
| 1.2.0 | 23 / 0 | |
| 1.1.1 | 19 / 0 | |
| 1.1.0 | 19 / 0 | |
| 1.0.1 | 15 / 0 | |
| 1.0.0 | 15 / 0 | |
| 0.0.4 | 0 / 23 | |
| 0.0.3 | 0 / 15 | |
| 0.0.2 | 0 / 14 |
v1.18.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.17.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.16.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.15.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.15.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.14.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.13.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.12.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.12.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.12.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.11.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.10.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.10.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.8.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.