The package has tests, a useful README, a matching MIT license, and no runtime dependencies. It lacks a security policy and has no recent repository activity, so pinning this version should be treated as a maintenance liability.
45%
Total Score
25
100
79
75
The latest release was over 8 years ago, with no releases in the last 12 months and only two releases overall. This is strong evidence of abandonment risk, although the package is not marked deprecated.
The repository recorded zero commits and zero active maintainers in the last 3 months, consistent with the long release gap and indicating no current maintenance capacity.
The registry namespace and repository owner match, but both identify an individual account rather than an organization, so there is no organizational backing to compensate for the inactive project.
Composer is used for builds, but no security-scanning tools are detected. The missing scanner is a modest hygiene gap and does not outweigh the stronger maintenance evidence.
The repository has no security policy, leaving vulnerability-reporting and response expectations undocumented. This is a transparency gap, though it is less serious than the prolonged inactivity.
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.