84%
Total Score
healthy
Frequent releases and active project backing outweigh unpinned workflow actions and the repository’s package-name mismatch.
The repository name does not match @zag-js/types and its README does not mention the package, so the package-to-repository relationship is less transparent; the monorepo context and organization backing partly compensate.
The repository uses established TypeScript, Vite, tsup, SWC, npm, and esbuild tooling; no security scanning tools were detected, leaving a modest transparency gap.
No repository security policy was detected, which reduces disclosure transparency, but the active repository and workflow audit provide some compensating project evidence.
All three workflows were analyzed with no detected injection or high-severity findings, but 8 of 9 action references are unpinned and one workflow grants top-level write permissions; this is a workflow hygiene caution, not a severe risk on its own.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
csstype Version 3.2.3 | — | — |
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.