The small package is easy to inspect, has a clear MIT license, a README, and no install-time scripts. It lacks security scanning and has no tests, while its long inactivity leaves maintenance and compatibility risk for adopters.
42%
Total Score
25
79
75
The latest release was published about eight years ago, with no releases in the last 12 months. Nine releases arrived in a brief 2018 window, but there is no evidence of ongoing maintenance.
The repository had zero commits and zero active maintainers in the last three months, consistent with the roughly eight-year release gap. This is strong evidence of abandonment risk even though the repository is not formally archived.
The registry namespace and repository are owned by the same individual account, providing direct ownership alignment but no organizational backing to compensate for the inactive maintenance record.
Composer is used as the build tool, but no security scanning tools were detected. For a small library this is a hygiene gap rather than a standalone reason to reject it.
The repository has no security policy, leaving no documented channel or process for reporting vulnerabilities. Combined with the inactive project, this weakens transparency and maintenance confidence.
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.