Install-time scripts add dependency-management risk, while the repository has no security scanning or security policy. The MIT declaration and intact repository keep this from being a more severe assessment.
38%
Total Score
33
100
72
50
The package has had no releases in the last 12 months, and its latest release was more than seven years ago. That strongly raises abandonment risk despite 29 historical releases.
The repository recorded zero commits and zero active maintainers in the last three months, consistent with the long release gap and indicating no current maintenance capacity.
The package runs post-install and post-update Composer scripts. These increase installation-time behavior and maintenance risk compared with a package without lifecycle scripts.
The registry namespace and repository owner match, but the owner is an individual account and no organizational backing is shown. This offers limited maintenance assurance.
There are no open issues or pull requests and no recent issue or pull-request activity. With zero recent commits, this supports the conclusion that the project is inactive rather than demonstrating efficient maintenance.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
composer/installers Version ~1.0 | — | — |
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.