Core logic for the slider widget implemented as a state machine
88%
Total Score
healthy
Active releases and an organization-backed repository outweigh workflow pinning and missing security documentation.
The repository name does not match the package name and its README does not mention @zag-js/slider, which creates some mapping uncertainty. The organization-backed monorepo context and the package's consistent source tree provide partial compensation.
The repository uses established build tools including TypeScript, Vite, tsup, SWC, npm scripts, and esbuild. No security scanning tools were detected, leaving a modest tooling gap.
The repository has no published security policy. This is a transparency and vulnerability-reporting gap, though the strong maintenance evidence limits its effect on adoption confidence.
All three workflows were analyzed with no audit findings or untrusted checkouts, but 8 of 9 action references are unpinned and one workflow grants top-level write permissions. With no untrusted trigger or sink, this is workflow hygiene rather than a severe risk.
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.