The package has had no commits or releases for over two years, and the repository has no security policy or scanning tools. Its MIT licensing, matching repository, documented release, and small focused dependency set provide useful transparency.
58%
Total Score
75
100
86
75
Only two releases exist, with no releases in the last 12 months and the latest published over two years ago. This is a meaningful maintenance concern, though the stable 1.0.1 release and focused module scope reduce the risk somewhat.
The repository recorded zero commits and zero active maintainers in the last three months, with its last push over two years ago. This strongly limits evidence of ongoing maintenance.
Composer is used for the build, but no security scanning tools are configured. The missing scanning is a hygiene gap rather than evidence that the release is unsafe.
The repository has no security policy. That weakens vulnerability-reporting transparency, although the package's license, README, and matching source repository provide other useful project information.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
magento/framework Version ^103.0 | — | — |
magento/module-store Version ^101.1 | — | — |
magento/module-backend Version ^102.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.