The project has had no release or repository activity for over eight years, and it lacks a security policy. Its MIT licensing, included tests, clear README, and small dependency footprint reduce adoption friction but do not offset the abandonment risk.
42%
Total Score
67
100
88
83
The package has only one release, published over eight years ago, with no releases in the last 12 months. This is strong evidence of abandonment risk for a dependency.
There were no commits and no active maintainers in the last three months, consistent with the repository having stopped after the initial release. This materially increases abandonment risk.
There has been no recent issue or pull request activity and no currently open work. With the matching long-term release inactivity, this supports a dormant-project assessment.
Composer build tooling is present, but no security scanning tooling is reported. For a small package this is a hygiene gap rather than evidence of immediate unfitness.
The repository has no security policy. This weakens vulnerability-reporting transparency, especially because the package has also shown no recent maintenance.
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.