@react-spectrum/tree
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:@swc/helpers | AI (phantom-deps): @swc/helpers is a known implicit runtime dependency of SWC-compiled code; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:@react-spectrum/text | AI (phantom-deps): Same-org monorepo dependency; expected pattern in React Spectrum packages. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Minimal README and no keywords are normal for monorepo-published component packages with centralized docs; not indicative of spam. | ai |
Versions (showing 16 of 16)
| Version | Deps | Published |
|---|---|---|
| 3.2.1 | 3 / 2 | |
| 3.2.0 | 3 / 0 | |
| 3.1.11 | 11 / 2 | |
| 3.1.10 | 11 / 2 | |
| 3.1.9 | 11 / 2 | |
| 3.1.8 | 11 / 2 | |
| 3.1.7 | 11 / 2 | |
| 3.1.6 | 11 / 2 | |
| 3.1.5 | 11 / 2 | |
| 3.1.4 | 11 / 2 | |
| 3.1.3 | 11 / 2 | |
| 3.1.2 | 11 / 2 | |
| 3.1.1 | 11 / 2 | |
| 3.1.0 | 11 / 2 | |
| 3.0.1 | 11 / 2 | |
| 3.0.0 | 11 / 2 |
v3.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.8
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.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.