Core logic for the tree-view widget implemented as a state machine
84%
Total Score
healthy
Frequent releases, active maintenance, and clear licensing outweigh mostly unpinned workflows and a weak package-to-repository match.
The repository name does not match the package and its README does not mention @zag-js/tree-view. This is plausible for a monorepo subpackage, but the missing explicit mention weakens source-to-package transparency.
The repository uses established TypeScript and build tooling, but no security scanning tools were detected, leaving a modest security-process gap.
No repository security policy was found. This weakens vulnerability-reporting transparency, but active maintenance and project documentation provide some compensation.
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, creating workflow hygiene 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.