@react-spectrum/tag
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 |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:pg | AI (typosquat): False positive: @react-spectrum/tag is an official Adobe React Spectrum scoped package with no relationship to the 'pg' PostgreSQL client. Name similarity is purely coincidental. | ai | |
| phantom-deps | phantom-dep:@swc/helpers | AI (phantom-deps): @swc/helpers is a known implicit runtime dependency for SWC-compiled packages; its presence in dependencies without direct imports is expected for this build toolchain. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Monorepo sub-packages in adobe/react-spectrum consistently lack keywords and verbose READMEs; these are not spam indicators for this well-established package family. | ai |
Versions (showing 35 of 35)
| Version | Deps | Published |
|---|---|---|
| 3.4.1 | 3 / 2 | |
| 3.4.0 | 3 / 0 | |
| 3.3.10 | 15 / 1 | |
| 3.3.9 | 15 / 1 | |
| 3.3.8 | 15 / 1 | |
| 3.3.7 | 15 / 1 | |
| 3.3.6 | 15 / 1 | |
| 3.3.5 | 15 / 1 | |
| 3.3.4 | 15 / 1 | |
| 3.3.3 | 15 / 1 | |
| 3.3.2 | 15 / 1 | |
| 3.3.1 | 15 / 1 | |
| 3.3.0 | 15 / 1 | |
| 3.2.15 | 15 / 1 | |
| 3.2.14 | 15 / 1 | |
| 3.2.13 | 15 / 1 | |
| 3.2.12 | 15 / 1 | |
| 3.2.11 | 15 / 1 | |
| 3.2.10 | 15 / 1 | |
| 3.2.9 | 15 / 1 | |
| 3.2.8 | 15 / 1 | |
| 3.2.7 | 15 / 1 | |
| 3.2.6 | 15 / 1 | |
| 3.2.5 | 15 / 1 | |
| 3.2.4 | 15 / 1 | |
| 3.2.3 | 15 / 1 | |
| 3.2.2 | 15 / 1 | |
| 3.2.1 | 15 / 1 | |
| 3.2.0 | 15 / 1 | |
| 3.1.4 | 15 / 1 | |
| 3.1.3 | 15 / 1 | |
| 3.1.2 | 15 / 1 | |
| 3.1.1 | 15 / 1 | |
| 3.1.0 | 15 / 1 | |
| 3.0.0 | 15 / 1 |
v3.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.5
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.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.2
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.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.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.