Modern type-safe way of building CLIs
72%
Total Score
67
100
85
80
100
The package is mature enough to have 32 releases over 812 days, but only 2 releases occurred in the last 12 months, indicating a slower maintenance cadence. This is a caution rather than a severe risk because the repository remains present and the package is not deprecated.
The repository reports 0 commits and 0 active maintainers over the last 3 months, a meaningful maintenance-momentum concern. The recent repository push and current release prevent this from being treated as abandonment on its own.
There are only 4 open issues and 1 open pull request; one issue was closed in the last month, but there were no new issues or pull requests and no merged pull requests in that period. This is mildly concerning but not independently severe.
TypeScript and Vitest build tooling are present, but no security scanning tools were detected. The build setup is positive, while the missing scanning is a security-hygiene gap rather than a health verdict by itself.
No repository security policy was found, reducing transparency about vulnerability reporting and response expectations. This is a genuine but non-severe governance gap.
We didn't find any vulnerabilities for this package.
No direct dependencies.
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.