Fix warning with usage of mcrypt-ext/magento2
38%
Total Score
unhealthy
Risky: no release since December 2018 and little visible project activity.
The package has only two releases, both from December 2018, with no releases in the last 12 months. This is strong evidence of abandonment risk for a dependency still being adopted today.
The artifact has no README, tests, or changelog, while the linked repository also reports no tests or changelog. Missing tests and changelog are normal for published artifacts, but the absent README reduces consumer transparency for this integration package.
The linked repository name does not match the package name, and no README mention was available. Although name differences can occur in subpackages, the lack of a matching reference leaves some uncertainty that the repository is the package's intended project home.
The repository has zero stars and forks and only one watcher. Popularity is supporting evidence rather than a verdict, but these values provide no visible community or adoption signal to offset the long inactivity.
Composer is used for the build, which fits the package ecosystem, but no security scanning tools are reported. This is a modest transparency gap rather than evidence that the package is unsafe.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
mcrypt-ext/magento2 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.