The small dependency surface, clear README, tests, and matching MIT license reduce adoption and inspection friction. Ongoing project oversight is limited, so future compatibility and fixes are uncertain.
42%
Total Score
25
100
80
75
The package has had only two releases, both in February 2017, with no releases in the last 12 months. That long release gap is strong evidence of abandonment risk, although the package is mature rather than experimental.
The repository recorded zero commits and zero active maintainers over the last three months, while its last push was over five years ago. The non-archived status does not compensate for this lack of observed maintenance.
There were no new or closed issues or pull requests in the last month, despite two open issues and six open pull requests. This suggests unresolved maintenance demand and limited project responsiveness.
The repository has no security policy and no security scanning tools. For a small package this is a hygiene gap rather than a standalone reason to reject it, but it weakens transparency around vulnerability handling.
We didn't find any vulnerabilities for this package.
No maintainer information available.
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.