There is no security policy, automated security scanning, or test suite, and the repository does not clearly identify the package. The MIT license and limited dependency set are positives, but they do not offset the thin maintenance evidence.
35%
Total Score
100
57
75
The package has only one release, published about four years ago, with no releases in the last 12 months. That is strong evidence of limited maintenance for a Magento module.
The repository name does not match the package name and its README does not mention the package. That makes the source relationship less transparent and warrants caution.
The repository has zero stars and forks and only one watcher. Popularity is not decisive, but these figures provide little supporting evidence of active community oversight.
Composer build tooling is present, but no security-scanning tools are configured. The absence of scanning reduces maintenance assurance, while the build tooling is a small compensating positive.
The repository is not archived, which keeps it technically available, but its last push was about four years ago and does not offset the lack of release activity.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
magento/framework Version ^103.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.