A clear README, matching source repository, and MIT licensing make the module transparent to integrate. Only one release and no commits or active maintainers in the last three months leave future maintenance uncertain. Organization ownership and no deprecation reduce, but do not remove, that concern.
57%
Total Score
75
100
88
75
The package has only one release, published about 383 days ago, with no releases in the last 12 months. That leaves little evidence of an established maintenance cadence.
The repository recorded zero commits and zero active maintainers over the last three months, which is a concrete sign that maintenance may have stalled.
Composer is used for the build, but no security scanning tools were detected. For a small module this is a hygiene gap rather than evidence of abandonment.
The repository has no published security policy, leaving vulnerability-reporting expectations unclear. This is a transparency weakness, not a standalone reason to reject the package.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
rkt/magento-data Version * | — | — |
magento/framework 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.