@react-spectrum/table
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-aria/grid | AI (phantom-deps): Declared dependency used indirectly through component composition; typical for monorepo-style packages. | ai | |
| phantom-deps | phantom-dep:@react-stately/grid | AI (phantom-deps): Declared dependency used indirectly through component composition; typical for monorepo-style packages. | ai | |
| phantom-deps | phantom-dep:@react-spectrum/button | AI (phantom-deps): Declared dependency from same org scope; used indirectly through re-exports or composition. | ai | |
| phantom-deps | phantom-dep:@react-stately/collections | AI (phantom-deps): Declared dependency used indirectly through component composition; typical for monorepo-style packages. | ai | |
| semgrep | semgrep:api-obfuscation-reflect | AI (semgrep): Standard Proxy/Reflect.get pattern for property delegation in a table layout component; publicly visible on GitHub, not obfuscation. | ai | |
| phantom-deps | phantom-dep:@swc/helpers | AI (phantom-deps): @swc/helpers is explicitly listed as a runtime dependency in package.json; this is the correct declaration pattern for SWC-compiled packages. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Established Adobe React Spectrum monorepo component; README/keywords signals are cosmetic and not indicative of spam for this package. | ai |
Versions (showing 51 of 57)
| Version | Deps | Published |
|---|---|---|
| 3.18.1 | 3 / 2 | |
| 3.18.0 | 3 / 0 | |
| 3.17.11 | 26 / 3 | |
| 3.17.10 | 26 / 3 | |
| 3.17.9 | 26 / 3 | |
| 3.17.8 | 26 / 3 | |
| 3.17.7 | 26 / 3 | |
| 3.17.6 | 26 / 3 | |
| 3.17.5 | 26 / 3 | |
| 3.17.4 | 26 / 3 | |
| 3.17.3 | 26 / 3 | |
| 3.17.2 | 26 / 3 | |
| 3.17.1 | 26 / 3 | |
| 3.17.0 | 26 / 3 | |
| 3.16.1 | 26 / 3 | |
| 3.16.0 | 26 / 3 | |
| 3.15.1 | 26 / 3 | |
| 3.15.0 | 26 / 3 | |
| 3.14.1 | 26 / 3 | |
| 3.14.0 | 26 / 3 | |
| 3.13.1 | 26 / 3 | |
| 3.13.0 | 26 / 3 | |
| 3.12.10 | 25 / 3 | |
| 3.12.9 | 25 / 3 | |
| 3.12.8 | 24 / 3 | |
| 3.12.7 | 24 / 3 | |
| 3.12.6 | 24 / 3 | |
| 3.12.5 | 24 / 3 | |
| 3.12.4 | 24 / 3 | |
| 3.12.3 | 24 / 3 | |
| 3.12.2 | 24 / 3 | |
| 3.12.1 | 28 / 3 | |
| 3.12.0 | 28 / 3 | |
| 3.11.1 | 28 / 3 | |
| 3.11.0 | 28 / 3 | |
| 3.10.0 | 27 / 3 | |
| 3.9.0 | 27 / 3 | |
| 3.8.0 | 27 / 3 | |
| 3.7.1 | 25 / 1 | |
| 3.7.0 | 25 / 1 | |
| 3.6.1 | 25 / 1 | |
| 3.6.0 | 25 / 1 | |
| 3.5.0 | 25 / 1 | |
| 3.4.0 | 25 / 1 | |
| 3.3.2 | 25 / 1 | |
| 3.3.1 | 25 / 1 | |
| 3.3.0 | 24 / 1 | |
| 3.2.0 | 25 / 1 | |
| 3.1.6 | 22 / 1 | |
| 3.1.5 | 22 / 1 | |
| 3.1.4 | 22 / 1 |
v3.18.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.18.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.17.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.17.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.17.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.17.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.17.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.17.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.17.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.17.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.17.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.17.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.17.1
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.1
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.1
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.1
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.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.12.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.12.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.12.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.12.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.12.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.12.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.12.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.12.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.12.1
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.0
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.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.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.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.0
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.