Core logic for the date-picker widget implemented as a state machine
82%
Total Score
healthy
Frequent releases and active repository work support this release; workflow action pinning and package linkage remain weaker.
No build attestation or trusted-publisher provenance was detected, so consumers have less evidence connecting the published artifact to the source build.
The repository name does not match the package and its README does not mention @zag-js/date-picker. A monorepo mismatch is ordinary, but the missing package reference leaves package ownership less transparent.
The project uses established TypeScript, Vite, tsup, SWC, npm, and esbuild tooling, but no security scanning tools were detected, leaving a modest security-process gap.
No repository security policy was found, reducing disclosure transparency even though the active project provides other maintenance evidence.
All three workflows were analyzed with no untrusted checkouts, script injection, or auditor findings, but 8 of 9 action references are unpinned and one workflow grants top-level write permissions.
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/popper Version 1.46.0 | — | — |
@zag-js/anatomy 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.