The MIT-versus-Apache licensing mismatch and lack of repository security tooling reduce transparency. The tiny module includes a README and a GitHub release, but offers little validation for a production dependency.
38%
Total Score
0
50
50
This package has only one release, published about 10 years ago, with no releases in the last 12 months. That strongly raises abandonment risk.
The repository recorded zero commits and zero active maintainers in the last three months, consistent with roughly 10 years since the last push and indicating strong abandonment risk.
The manifest declares Apache-2.0 while the artifact license file is recognized as MIT; although a license is present, the mismatch reduces clarity for adopters.
Composer build tooling is present, but no security scanning tools were detected. This is a transparency and maintenance gap, though not evidence that the package is unsafe by itself.
The repository has no security policy, leaving vulnerability reporting and response expectations undocumented. The long period without activity makes this gap more consequential.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
magento/magento-composer-installer 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.