Core logic for the checkbox widget implemented as a state machine
84%
Total Score
healthy
Frequent releases, active maintenance, and strong packaging outweigh unpinned workflow actions and weak package-to-repository identification.
The release has no registry build attestation or trusted-publisher identity, leaving publication provenance less transparent than it could be.
The repository name does not match the package and its README does not mention @zag-js/checkbox, so the package-to-repository link is less directly demonstrated; this is somewhat mitigated by the organization-backed monorepo context.
The repository uses established TypeScript and modern build tools, but no security scanning tools were detected, leaving a modest security-process gap.
No repository security policy was detected, reducing the project's published guidance for reporting vulnerabilities.
All three workflows were analyzed with no audit findings, no untrusted checkouts, and no script injection. However, 8 of 9 action references are unpinned and one workflow grants top-level write permissions, creating a workflow-hygiene caution.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
@zag-js/core Version 1.46.0 | — | — |
@zag-js/types Version 1.46.0 | — | — |
@zag-js/utils Version 1.46.0 | — | — |
@zag-js/anatomy Version 1.46.0 | — | — |
@zag-js/dom-query Version 1.46.0 | — | — |
Connect your repositories to instantly see whether vulnerable or malicious packages exist in your codebase.
Free. No credit card required.

I consent to receiving marketing communications based on Aikido’s Privacy Policy.
SOC 2Compliant
ISO 27001Compliant
ISO 42001Compliant© All Intel data is openly available and commercially licensed.