The package is small and easy to inspect, with one runtime dependency, a license, and no install-time scripts. Its only release was nearly 12 years ago, repository commits stopped about 10 years ago, and the repository does not clearly identify this package. The missing security policy adds a smaller transparency concern.
38%
Total Score
25
100
63
75
There has been only one release, published nearly 12 years ago, with no releases in the last 12 months. That is strong evidence of abandonment for a package intended to remain a maintained dependency.
There were zero commits and zero active maintainers in the last three months, consistent with a project that has been inactive for years. This materially increases abandonment risk.
Four issues remain open, while there were no new or closed issues and no pull-request activity in the last month. This suggests unresolved maintenance needs, though it is weaker evidence than the release and commit history.
The repository name does not match the package name and its README does not mention the package. That weakens confidence that the linked source repository directly belongs to this published package.
The repository has zero stars and forks and only one watcher. Popularity is supporting evidence rather than a verdict, but these counts provide no community-maintenance offset.
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.