Clear licensing, documentation, and repository tests make the package easier to understand and maintain. Its stable API and organization-backed repository help, but the long-standing lack of releases or commits makes future fixes uncertain.
42%
Total Score
63
100
72
83
The package has had only two releases, with the latest in February 2016 and none in the last 12 months. This is strong evidence of abandonment risk for a dependency needing future fixes.
There were no commits and no active maintainers in the last three months, consistent with the repository's last push in 2017. This materially increases the risk that defects will remain unresolved.
The repository has 20 open issues and no issues or pull requests were closed in the last month, indicating an unresolved maintenance backlog.
The repository has four stars and one fork, providing little evidence of a broad support community. Popularity is supporting evidence, so this is a modest concern rather than the main risk.
Composer build tooling is present, but no security scanning tools were detected. This is a hygiene gap, though the long absence of maintenance weighs more heavily.
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.