@radix-ui/react-toggle-group
View docs [here](https://radix-ui.com/primitives/docs/components/toggle-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 legitimate Radix UI / WorkOS team restructuring; chancestrickland is a long-standing, well-approved publisher in the ecosystem. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): New maintainers (andy-hook, hadihallak, chancestrickland, mark-workos) are consistent with the WorkOS team maintaining Radix UI primitives. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Removed maintainers reflect a legitimate team transition within the Radix UI / WorkOS organization, not a hostile takeover. | ai | |
| provenance | no-provenance | AI (provenance): Radix UI packages historically publish without Sigstore provenance; consistent with all prior versions of this package. | ai | |
| phantom-deps | phantom-dep:@radix-ui/primitive | AI (phantom-deps): Same-org dependency declared but used indirectly; consistent with Radix UI's internal package structure. | ai |
Versions (showing 27 of 27)
| Version | Deps | Published |
|---|---|---|
| 1.1.11 | 7 / 9 | |
| 1.1.3 | 7 / 8 | |
| 1.1.2 | 7 / 8 | |
| 1.1.1 | 7 / 0 | |
| 1.1.0 | 7 / 0 | |
| 1.0.4 | 8 / 0 | |
| 1.0.3 | 8 / 0 | |
| 1.0.2 | 8 / 0 | |
| 1.0.1 | 8 / 0 | |
| 1.0.0 | 8 / 0 | |
| 0.1.5 | 7 / 0 | |
| 0.1.4 | 7 / 0 | |
| 0.1.3 | 7 / 0 | |
| 0.1.2 | 7 / 0 | |
| 0.1.1 | 7 / 0 | |
| 0.1.0 | 7 / 0 | |
| 0.0.11 | 9 / 0 | |
| 0.0.10 | 9 / 0 | |
| 0.0.9 | 9 / 0 | |
| 0.0.8 | 9 / 0 | |
| 0.0.7 | 9 / 0 | |
| 0.0.6 | 8 / 0 | |
| 0.0.5 | 8 / 0 | |
| 0.0.4 | 8 / 0 | |
| 0.0.3 | 8 / 0 | |
| 0.0.2 | 8 / 0 | |
| 0.0.1 | 7 / 0 |
v1.1.11
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.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.3
2 findingsThis version was published by a different npm account than previous versions on 2025-04-08. 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.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.
v1.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.
v1.1.0
2 findingsThis 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.3
2 findings[Accepted risk] Package 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-12-10. This could indicate a legitimate maintainer transition or an account compromise.
v0.1.2
2 findings[Accepted risk] Package 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-12-09. This could indicate a legitimate maintainer transition or an account compromise.
v0.1.1
2 findings[Accepted risk] Package 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
2 findings[Accepted risk] Package 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-09-07. This could indicate a legitimate maintainer transition or an account compromise.
v0.0.11
2 findings[Accepted risk] Package 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-08-04. This could indicate a legitimate maintainer transition or an account compromise.
v0.0.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.5
2 findings[Accepted risk] Package 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-03-24. This could indicate a legitimate maintainer transition or an account compromise.
v0.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.