@radix-ui/react-label
View docs [here](https://radix-ui.com/primitives/docs/utilities/label).
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 |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): chancestrickland is a long-standing WorkOS/Radix UI contributor with strong approval history; publisher change reflects legitimate internal team transition, not compromise. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): New maintainers chancestrickland and mark-workos are established WorkOS team members; addition is consistent with legitimate org restructuring. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Removed maintainers reflect the same WorkOS team transition; no evidence of hostile takeover given clean package content and repo metadata. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Radix UI packages consistently omit descriptions in package.json; this is a stable pattern across the entire primitives monorepo, not a malicious signal. | ai |
Versions (showing 30 of 30)
| Version | Deps | Published |
|---|---|---|
| 2.1.8 | 1 / 9 | |
| 2.1.3 | 1 / 8 | |
| 2.1.2 | 1 / 8 | |
| 2.1.1 | 1 / 0 | |
| 2.1.0 | 1 / 0 | |
| 2.0.2 | 2 / 0 | |
| 2.0.1 | 2 / 0 | |
| 2.0.0 | 2 / 0 | |
| 1.0.0 | 5 / 0 | |
| 0.1.5 | 5 / 0 | |
| 0.1.4 | 5 / 0 | |
| 0.1.3 | 5 / 0 | |
| 0.1.2 | 5 / 0 | |
| 0.1.1 | 5 / 0 | |
| 0.1.0 | 4 / 0 | |
| 0.0.15 | 5 / 0 | |
| 0.0.14 | 5 / 0 | |
| 0.0.13 | 5 / 0 | |
| 0.0.12 | 5 / 0 | |
| 0.0.11 | 5 / 0 | |
| 0.0.10 | 5 / 0 | |
| 0.0.9 | 5 / 0 | |
| 0.0.8 | 5 / 0 | |
| 0.0.7 | 5 / 0 | |
| 0.0.6 | 4 / 0 | |
| 0.0.5 | 4 / 0 | |
| 0.0.4 | 4 / 0 | |
| 0.0.3 | 4 / 0 | |
| 0.0.2 | 4 / 0 | |
| 0.0.1 | 3 / 1 |
v2.1.8
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: chancestrickland.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.2
2 findingsThis version was published by a different npm account than previous versions on 2025-02-05. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.1
2 findingsThis version was published by a different npm account than previous versions on 2024-12-13. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2024-06-19. This could indicate a legitimate maintainer transition or an account compromise.
v2.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2022-07-20. This could indicate a legitimate maintainer transition or an account compromise.
v0.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.