← Home

@radix-ui/react-checkbox

npm Repository Homepage

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

6
Versions
MIT
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures No source commit

Maintainers

hadihallakchancestricklandmark-workosnpm-workos

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Legitimate transition to GitHub Actions CI/CD publishing for the radix-ui org. ai
maintainer-change maintainer-added AI (maintainer-change): WorkOS acquired Radix UI; npm-workos is the new organizational account. ai
maintainer-change maintainer-removed AI (maintainer-change): Previous individual maintainers replaced by org account after WorkOS acquisition. ai
npm-metadata no-description AI (npm-metadata): Radix UI component packages historically have minimal descriptions. ai
bogus-package bogus-package AI (bogus-package): False positive on a 43M downloads/week established package. ai

Versions (showing 6 of 6)

Version Deps Published
1.3.5 8 / 7
1.3.4 8 / 7
1.3.3 8 / 9
1.3.2 8 / 9
1.3.1 8 / 9
1.3.0 8 / 9

v1.3.5

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v1.3.4

2 findings
HIGH Publisher changed: chancestrickland → GitHub Actions (on 2026-06-06) provenance

This version was published by a different npm account than previous versions on 2026-06-06. This could indicate a legitimate maintainer transition or an account compromise.

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v1.3.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.

v1.3.2

1 finding
LOW No provenance attestation provenance

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

v1.3.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.

v1.3.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.