@radix-ui/react-radio-group
View docs [here](https://radix-ui.com/primitives/docs/components/radio-group).
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): Publisher change reflects a legitimate internal Radix UI/WorkOS team transition; chancestrickland is a long-standing ecosystem participant with strong approval history. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): New maintainers chancestrickland and mark-workos are consistent with the Radix UI/WorkOS organization; legitimate team restructuring. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Removed maintainers are consistent with a legitimate internal team transition at WorkOS/Radix UI, not a hostile takeover. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Early Radix UI primitive packages did not include descriptions; this is a stable pattern for this package family, not a malware indicator. | ai | |
| dependencies | unvetted-dep:@radix-ui/react-roving-focus | AI (dependencies): @radix-ui/react-roving-focus is a sibling package from the same radix-ui/primitives monorepo; not a suspicious dependency. | ai |
Versions (showing 35 of 35)
| Version | Deps | Published |
|---|---|---|
| 1.2.4 | 10 / 8 | |
| 1.2.3 | 10 / 8 | |
| 1.2.2 | 10 / 0 | |
| 1.2.1 | 10 / 0 | |
| 1.2.0 | 10 / 0 | |
| 1.1.3 | 11 / 0 | |
| 1.1.2 | 11 / 0 | |
| 1.1.1 | 11 / 0 | |
| 1.1.0 | 11 / 0 | |
| 1.0.0 | 12 / 0 | |
| 0.1.5 | 11 / 0 | |
| 0.1.4 | 11 / 0 | |
| 0.1.3 | 11 / 0 | |
| 0.1.2 | 11 / 0 | |
| 0.1.1 | 11 / 0 | |
| 0.1.0 | 11 / 0 | |
| 0.0.19 | 13 / 0 | |
| 0.0.18 | 13 / 0 | |
| 0.0.17 | 14 / 0 | |
| 0.0.16 | 12 / 0 | |
| 0.0.15 | 12 / 0 | |
| 0.0.14 | 11 / 0 | |
| 0.0.13 | 11 / 0 | |
| 0.0.12 | 11 / 0 | |
| 0.0.11 | 11 / 0 | |
| 0.0.10 | 11 / 0 | |
| 0.0.9 | 10 / 0 | |
| 0.0.8 | 10 / 0 | |
| 0.0.7 | 10 / 0 | |
| 0.0.6 | 7 / 0 | |
| 0.0.5 | 7 / 0 | |
| 0.0.4 | 7 / 0 | |
| 0.0.3 | 7 / 0 | |
| 0.0.2 | 7 / 0 | |
| 0.0.1 | 6 / 1 |
v1.2.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.2
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.
v1.2.1
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-10-01. This could indicate a legitimate maintainer transition or an account compromise.
v1.2.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.
v1.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.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.1.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.1
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 2021-10-14. This could indicate a legitimate maintainer transition or an account compromise.
v0.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.5
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.
v0.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.