← Home

@radix-ui/react-toggle

npm Repository Homepage

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

55
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 legitimate WorkOS/Radix UI team transition; chancestrickland is a long-standing ecosystem contributor with strong approval history. ai
maintainer-change maintainer-added AI (maintainer-change): New maintainers chancestrickland and mark-workos are consistent with Radix UI being a WorkOS project; legitimate organizational transition. ai
maintainer-change maintainer-removed AI (maintainer-change): Removal of previous maintainers is consistent with the documented WorkOS team transition for Radix UI primitives. ai
npm-metadata no-description AI (npm-metadata): Radix UI packages consistently omit descriptions in package.json; not a malware indicator for this well-established package family. ai
provenance no-provenance AI (provenance): Radix UI primitives do not currently publish with Sigstore provenance; consistent across the package family and not a risk indicator here. ai

Versions (showing 55 of 55)

Hide prereleases
Version Deps Published
1.1.4 3 / 9
1.1.3 3 / 8
1.1.2 3 / 8
1.1.1 3 / 0
1.1.0 3 / 0
1.0.3 4 / 0
1.0.2 4 / 0
1.0.1 4 / 0
1.0.0 4 / 0
0.1.4 4 / 0
0.1.3 4 / 0
0.1.2 4 / 0
0.1.1 4 / 0
0.1.0 4 / 0
0.0.10 5 / 0
0.0.9 5 / 0
0.0.8 5 / 0
0.0.7 5 / 0
0.0.6 5 / 0
0.0.5 5 / 0
0.0.4 5 / 0
0.0.3 5 / 0
0.0.2 5 / 0
0.0.1 4 / 0
1.1.10-rc.1761760880074 3 / 9
1.1.10-rc.1761757765388 3 / 9
1.1.10-rc.1761752560860 3 / 9
1.1.10-rc.1761750294484 3 / 9
1.1.10-rc.1761750045307 3 / 9
1.1.10-rc.1761621280215 3 / 9
1.1.10-rc.1761620575619 3 / 9
1.1.10-rc.1761619701743 3 / 9
1.1.10-rc.1761615925003 3 / 9
1.1.10-rc.1761614930803 3 / 9
1.1.10-rc.1761614469962 3 / 9
1.1.10-rc.1761582029795 3 / 9
1.1.10-rc.1761327012562 3 / 9
1.1.10-rc.1755205432459 3 / 9
1.1.10-rc.1755201399387 3 / 9
1.1.10-rc.1755118410828 3 / 9
1.1.10-rc.1755114563302 3 / 9
1.1.10-rc.1752791004720 3 / 9
1.1.10-rc.1752166910601 3 / 9
1.1.10-rc.1752166434368 3 / 9
1.1.10-rc.1752166197873 3 / 9
1.1.10-rc.1752165236204 3 / 9
1.1.9-rc.1747678980544 3 / 9
1.1.9-rc.1746560904918 3 / 9
1.1.7-rc.1746466567086 3 / 9
1.1.7-rc.1746075822931 3 / 9
1.1.7-rc.1746053194630 3 / 9
1.1.7-rc.1746044551800 3 / 9
1.1.7-rc.1745972185559 3 / 9
1.1.7-rc.1745439717073 3 / 9
1.1.7-rc.1745345395380 3 / 9

v1.1.4

2 findings
HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: chancestrickland.

INFO No provenance attestation provenance

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

v1.1.3

1 finding
INFO No provenance attestation provenance

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

v1.1.2

1 finding
INFO No provenance attestation provenance

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

v1.1.1

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

2 findings
INFO No provenance attestation provenance

[Accepted risk] 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.0.3

1 finding
INFO No provenance attestation provenance

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

v1.0.2

1 finding
INFO No provenance attestation provenance

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

v1.0.1

1 finding
INFO No provenance attestation provenance

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

v1.0.0

2 findings
INFO No provenance attestation provenance

[Accepted risk] 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.4

1 finding
INFO No provenance attestation provenance

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

v0.1.3

1 finding
INFO No provenance attestation provenance

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

v0.1.2

1 finding
INFO No provenance attestation provenance

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

v0.1.1

2 findings
INFO No provenance attestation provenance

[Accepted risk] 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

2 findings
INFO No provenance attestation provenance

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

INFO Publisher changed: andy-hook → benoitgrelard (on 2021-09-07) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2021-09-07. This could indicate a legitimate maintainer transition or an account compromise.

v0.0.10

2 findings
INFO No provenance attestation provenance

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

INFO Publisher changed: benoitgrelard → andy-hook (on 2021-08-04) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2021-08-04. This could indicate a legitimate maintainer transition or an account compromise.

v0.0.9

1 finding
INFO No provenance attestation provenance

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

v0.0.8

1 finding
INFO No provenance attestation provenance

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

v0.0.7

1 finding
INFO No provenance attestation provenance

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

v0.0.6

2 findings
INFO No provenance attestation provenance

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

INFO Publisher changed: jjenzz → benoitgrelard (on 2021-03-26) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2021-03-26. This could indicate a legitimate maintainer transition or an account compromise.

v0.0.5

2 findings
INFO No provenance attestation provenance

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

INFO Publisher changed: benoitgrelard → jjenzz (on 2021-03-24) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2021-03-24. This could indicate a legitimate maintainer transition or an account compromise.

v0.0.4

1 finding
INFO No provenance attestation provenance

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

v0.0.3

1 finding
INFO No provenance attestation provenance

[Accepted risk] 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
INFO No provenance attestation provenance

[Accepted risk] 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
INFO No provenance attestation provenance

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