Its license, tests, and stable version are reassuring, while the repository has no security policy or workflow automation. Pinning this exact version is safer than tracking future updates from this inactive source.
42%
Total Score
50
100
81
83
The repository recorded zero commits and zero active maintainers in the last three months. Combined with the old last push, this materially increases abandonment risk.
The package has 89 releases overall, but none in the last 12 months; its latest release was nearly six years ago. This is strong evidence of abandonment risk despite the established release count.
The repository name does not match the package name and its README does not mention the package, so the source may not clearly belong to this release. Organization backing reduces but does not remove that concern.
Composer build tooling is present, but no security scanning tools were detected. For a large Magento extension, that is a modest transparency and maintenance gap.
No repository security policy was found. This weakens the project's published process for handling vulnerabilities, though it is less severe than inactivity or archival.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
magento/framework Version >=103.0.0 | — | — |
magento/module-store Version >=101.1.0 | — | — |
magento/module-backend Version >=102.0.0 | — | — |
magento/module-catalog Version >=104.0.0 | — | — |
elasticsearch/elasticsearch Version ~6.7|~7.2 | — | — |
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.