The repository is still present, the package has documentation and release notes, and it is not deprecated. The license files conflict with the declared license, while recent commit and release activity is absent and no security tooling or policy is provided.
58%
Total Score
50
75
50
The latest registry release was 1.0.7 on March 2, 2017, with no releases in the last 12 months. This substantially raises maintenance and compatibility risk, although the linked repository was pushed more recently.
The artifact contains a license file and the repository also has one, but the manifest declares OSL-3.0 while the detected license is GPL-3.0. That mismatch requires legal clarification before adoption.
There were zero commits and zero active maintainers in the three months before collection. Combined with no recent registry releases, this indicates weak current maintenance despite the later repository push.
The repository uses Composer, but no security scanning tool was detected. This is a transparency and hygiene gap, not evidence that the package is unsafe.
The repository has no security policy, leaving vulnerability reporting and response expectations unspecified. This lowers transparency for a package integrated into production systems.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
magento-hackathon/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.