The package is small, tested, and clearly licensed, with no install-time scripts. Its lone maintainer, absent security policy, unpinned workflow actions, and repository naming mismatch add adoption risk.
48%
Total Score
50
60
67
The latest release was over 10 years ago, with no releases in the last 12 months; this is strong evidence of abandonment despite the package having four historical releases.
Only one registry account has publish access. The individual ownership context provides limited maintenance redundancy, although access records alone do not prove inactivity.
There are two open issues and one open pull request, but no issues or pull requests were created or closed in the last month, offering little evidence of active support.
The repository name does not match the package name and its README does not mention the package, so the source-to-artifact relationship is less transparent than expected.
The repository is not archived, which preserves some adoption confidence, but it was last pushed about 4 years ago and does not offset the long release 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.