MIT licensing, a substantial README, and one runtime dependency are reassuring, but the single-user project has no security policy. Treat this as a legacy fork rather than an actively supported dependency.
40%
Total Score
50
100
80
75
Only one registry maintainer account is listed. Because project backing identifies a personal account rather than an organization, there is limited visible publishing redundancy.
The package has had only 2 releases, both around 5 years ago, with no releases in the last 12 months. That makes ongoing maintenance and compatibility uncertain.
The repository recorded 0 commits and 0 active maintainers in the last 3 months, consistent with the long release gap and increased abandonment risk.
The repository has 0 stars, 0 forks, and 1 watcher. Popularity is not decisive, but these figures provide little supporting evidence of community review or backup maintenance.
The linked repository has no security policy, reducing transparency about how vulnerabilities should be reported and handled.
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.