The package is clearly identified, licensed, and documented, with a small dependency surface and no install-time scripts. Its single-maintainer project and absent security scanning provide little resilience, so this old release carries substantial maintenance risk.
43%
Total Score
67
100
83
88
The registry namespace and repository are owned by the same individual account, which is consistent with a small personal project. It provides less organizational continuity than company-backed maintenance.
The latest registry release was over 7 years ago, with no releases in the last 12 months. This is strong evidence of abandonment risk for a package intended for ongoing use.
The repository recorded 0 commits and 0 active maintainers in the last 3 months, consistent with the long release gap and indicating no current maintenance capacity.
The repository has only 3 stars, 1 fork, and 1 watcher. Low adoption is not decisive, but it provides little supporting evidence of community resilience.
Composer is used for builds, which is positive, but no security scanning tools are present. The missing scanning reduces maintenance and vulnerability-detection assurance.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
composer/installers Version >=1.0.8 | — | — |
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.