Its MIT license, minimal dependency surface, and clear package/repository match reduce adoption friction. The lone maintainer and absent security policy leave little evidence of ongoing stewardship.
42%
Total Score
25
100
71
83
The latest release was nearly nine years ago, with no releases in the last 12 months. That prolonged pause is strong evidence of abandonment risk, despite the package having 10 historical releases.
The repository recorded zero commits and zero active maintainers over the last three months, consistent with the nearly nine-year release gap. This materially increases maintenance and abandonment risk.
Registry publishing access is held by one account, which limits visible publishing redundancy. The repository is user-owned rather than organization-backed, so there is no provided evidence of a broader maintenance team to compensate.
Composer is used for build or package management, but no security-scanning tooling is present. The missing scanning is a hygiene gap, although it does not by itself show that the release is unsafe.
The repository has no security policy or documented vulnerability-reporting process. For a library containing security-related utilities, this is a meaningful transparency 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.