MIT licensing, a small dependency footprint, repository tests, and a matching source repository improve transparency. The sole release was about six years ago, with no commits in the last three months, indicating substantial abandonment risk.
40%
Total Score
50
100
75
75
This package has only one release, published about six years ago, with no releases in the last 12 months. That is strong evidence of a potentially abandoned dependency.
There were no commits and no active maintainers in the last three months. Combined with the one-release history, this materially increases abandonment risk.
The repository uses Composer build tooling, but no security scanning tools were detected. The missing scanning is a modest hygiene gap, not evidence that the package is unsafe.
The linked repository is not archived, which is a positive counterpoint to the stale activity. Its last push was still about six years ago, so this does not establish active maintenance.
The repository has no security policy, leaving vulnerability reporting and response expectations undocumented. This is a transparency gap, though the package's long inactivity is the larger concern.
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.