@radix-ui/react-toggle
View docs [here](https://radix-ui.com/primitives/docs/components/toggle).
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | missing-githead | AI (provenance): Package has SLSA provenance; missing gitHead is a metadata quirk, not a security signal. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Radix UI primitives consistently have minimal READMEs and no keywords; stable FP for this package. | 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 | |
| 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 | |
| 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 | |
| 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 | |
| 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 |
Versions (showing 36 of 36)
| Version | Deps | Published |
|---|---|---|
| 1.1.18 | 3 / 7 | |
| 1.1.17 | 3 / 7 | |
| 1.1.16 | 3 / 7 | |
| 1.1.15 | 3 / 7 | |
| 1.1.14 | 3 / 7 | |
| 1.1.13 | 3 / 7 | |
| 1.1.12 | 3 / 7 | |
| 1.1.11 | 3 / 7 | |
| 1.1.10 | 3 / 9 | |
| 1.1.9 | 3 / 9 | |
| 1.1.8 | 3 / 9 | |
| 1.1.7 | 3 / 9 | |
| 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 |
v1.1.18
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.1.17
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.1.16
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.1.15
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.1.14
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.1.13
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: GitHub Actions.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.1.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.