The codebase is small, licensed, tested, and has no install-time scripts, but it has no recent maintenance or security policy. Its single-person ownership leaves little visible backup.
43%
Total Score
25
100
92
75
The repository has had zero commits and zero active maintainers in the last 3 months, and was last pushed about 7 years ago. The inactive source confirms that maintenance is not ongoing.
Only one registry publishing account is listed, and the repository is owned by an individual rather than an organization. This provides little visible maintainer redundancy, though the registry list alone does not prove inactivity.
The package has had only one release, published about 9 years ago, with no releases in the last 12 months. That strongly raises abandonment risk for a dependency.
The repository has no security policy, leaving vulnerability reporting and response expectations undocumented. This is a transparency gap, especially for a package with no recent maintenance evidence.
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.