Clear documentation, licensing, tests, and a minimal runtime dependency make integration straightforward. Maintenance evidence is stale, with no releases for about nine years and no recent commits; the repository/package naming mismatch also reduces transparency.
58%
Total Score
50
100
67
83
Only four releases have been published since October 2013, with no release in about nine years and no releases in the last 12 months. The long release gap is substantial abandonment evidence, even though the package is not marked deprecated.
The repository recorded zero commits and zero active maintainers during the last three months. This corroborates the very old registry release rather than showing active maintenance.
There were no new or closed issues or pull requests in the last month, while three issues and one pull request remain open. This indicates little current project activity.
The repository name does not match the package name and its README does not mention the package, creating uncertainty about whether it is the intended source repository. The mismatch is more concerning because the README also refers to a different project name.
Composer is used for the build, but no security scanning tools are reported. The missing scanning is a hygiene gap, not a standalone dependency decision blocker.
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.