The stable version, minimal runtime dependency, matching repository, README, changelog, and GPL-2.0 license make the package understandable to integrate. Its single maintainer, absent security policy, and no security scanning leave limited ongoing oversight.
42%
Total Score
25
100
81
50
The package has had no release in more than nine years: its latest release was January 2017, with zero releases in the last 12 months. This is strong evidence of abandonment risk despite a previously regular release interval.
The repository recorded zero commits and zero active maintainers in the last three months, consistent with the long release gap and indicating no observed ongoing maintenance.
Only one registry maintainer is listed. This limits the visible publishing base and increases continuity risk, although the repository is directly owned by the same individual.
Composer is used as a build tool, but no security scanning tools are present. The lack of scanning is a modest hygiene gap rather than evidence of an unsafe release.
The repository has no security policy, so there is no documented process for receiving or handling vulnerability reports. This is a transparency and maintenance gap for a plugin used in applications.
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.