The small repository footprint and lack of security tooling leave limited evidence for long-term support. Clear licensing, documentation, and repository tests help, but do not offset the package's age and inactivity.
38%
Total Score
25
75
75
The package has only one release, published about 10 years and 9 months ago, with no releases in the last 12 months. This is strong evidence that the dependency is no longer actively maintained.
The repository recorded zero commits and zero active maintainers in the last 3 months, and its last push was in March 2016. The absence of recent source changes materially increases abandonment risk.
There were no new issues, closed issues, pull requests, or merged pull requests in the last month. While issue counts are partly unknown, the available activity shows no current maintenance signal.
Composer build tooling is present, but no security-scanning tools were detected. This is a modest transparency and maintenance gap for a package with no recent activity.
The linked repository has no security policy. That weakens vulnerability-reporting transparency, although it is less important than the clear evidence of long-term inactivity.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
composer/installers Version * | — | — |
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.