Get npm package metadata
78%
Total Score
70
100
95
67
100
Only one registry publisher is listed, which creates some publishing concentration; repository activity shows a second active contributor, partly offsetting the concern.
The repository is owned by an individual rather than an organization, so the single registry publisher and concentrated ownership provide less institutional maintenance redundancy.
Six issues and three pull requests remain open, while none were opened or closed in the past month; this is a mild sign of limited recent issue throughput, but not abandonment given the release and commit activity.
The project uses TypeScript, Vitest, Vite, and npm scripts with a build tool, indicating a structured development process; no security scanner is configured, leaving a modest hygiene gap.
The repository has no security policy, reducing transparency about vulnerability reporting and response expectations.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
cac Version ^7.0.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.