The package documents its local-development scope clearly and has a stable MIT declaration. Ongoing maintenance is uncertain because the repository has had no commits in three months and only one registry maintainer, with no security policy or scanning.
61%
Total Score
50
88
50
Only one account has registry publish access. Because the project is user-owned rather than organization-backed, this leaves a thin publishing base and increases continuity risk.
The package has only two releases, both published about 149 days ago and within the same day, with no subsequent release activity. This provides limited evidence of sustained maintenance.
The repository recorded zero commits and zero active maintainers during the last three months. Combined with the short release history, this is a meaningful sign that ongoing maintenance may have stopped.
Composer is used for the build, which fits the package ecosystem, but no security-scanning tooling was detected. That is a modest transparency and maintenance weakness rather than evidence of a severe problem.
The repository has no security policy. This makes vulnerability reporting and response expectations less clear for a package that changes authentication behavior.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
magento/framework Version >=103.0 | — | — |
magento/module-user Version * | — | — |
magento/module-config Version * | — | — |
magento/module-backend Version * | — | — |
magento/module-authorization 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.