← Home

@radix-ui/react-radio-group

npm Repository Homepage

View docs [here](https://radix-ui.com/primitives/docs/components/radio-group).

70
Versions
MIT
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

benoitgrelardstephenhaneyandy-hookhadihallakchancestricklandmark-workos

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
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 70 of 70)

Hide prereleases
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
1.3.9-rc.1766004502650 10 / 9
1.3.9-rc.1762291353631 10 / 9
1.3.9-rc.1762290574118 10 / 9
1.3.8-rc.1761760880074 10 / 9
1.3.8-rc.1761757765388 10 / 9
1.3.8-rc.1761752560860 10 / 9
1.3.8-rc.1761750294484 10 / 9
1.3.8-rc.1761750045307 10 / 9
1.3.8-rc.1761621280215 10 / 9
1.3.8-rc.1761620575619 10 / 9
1.3.8-rc.1761619701743 10 / 9
1.3.8-rc.1761615925003 10 / 9
1.3.8-rc.1761614930803 10 / 9
1.3.8-rc.1761614469962 10 / 9
1.3.8-rc.1761582029795 10 / 9
1.3.8-rc.1761327012562 10 / 9
1.3.8-rc.1755205432459 10 / 9
1.3.8-rc.1755201399387 10 / 9
1.3.8-rc.1755118410828 10 / 9
1.3.8-rc.1755114563302 10 / 9
1.3.8-rc.1752791004720 10 / 9
1.3.8-rc.1752166910601 10 / 9
1.3.8-rc.1752166434368 10 / 9
1.3.8-rc.1752166197873 10 / 9
1.3.8-rc.1752165236204 10 / 9
1.3.7-rc.1747678980544 10 / 9
1.3.7-rc.1746560904918 10 / 9
1.3.5-rc.1746466567086 10 / 9
1.3.5-rc.1746075822931 10 / 9
1.3.5-rc.1746053194630 10 / 9
1.3.5-rc.1746044551800 10 / 9
1.3.5-rc.1745972185559 10 / 9
1.3.5-rc.1745439717073 10 / 9
1.3.5-rc.1745345395380 10 / 9
1.3.4-rc.1745339201309 10 / 9

v1.2.4

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.2.3

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.2.2

2 findings
HIGH Publisher changed: benoitgrelard → chancestrickland (on 2024-12-13) provenance

This 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.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.2.1

2 findings
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: vladmoroz → chancestrickland (on 2024-10-01) provenance

[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 findings
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: benoitgrelard → vladmoroz (on 2024-06-19) provenance

[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 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.1.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.1.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.1.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.0

2 findings
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: jjenzz → benoitgrelard (on 2022-07-20) provenance

[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 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.4

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.3

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.1

2 findings
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: benoitgrelard → jjenzz (on 2021-10-14) provenance

[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 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.19

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.18

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.17

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.16

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.15

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.14

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.13

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.12

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.11

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.10

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.9

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.8

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.7

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.6

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.5

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.4

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.3

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.