Documentation and licensing are in place, and the repository is backed by an organization. There is no security policy or automated security scanning, so ongoing oversight is limited.
62%
Total Score
83
88
50
This is the package's only release, published less than a day ago, so there is no release track record yet. Its newness limits evidence of long-term maintenance but does not indicate abandonment by itself.
The repository has no commits or active maintainers in the last three months, although the repository was pushed recently and the package is newly published. This leaves ongoing maintenance unproven.
Composer build tooling is present, but no security scanning tools were detected. That leaves dependency and code checks less visible for a package handling storefront and customer-activity functionality.
The repository has no security policy, which reduces transparency for reporting and handling vulnerabilities. This is a hygiene and oversight gap rather than evidence of a security incident.
| Dependency | Last Release | Score |
|---|---|---|
magento/framework Version ^103.0 | — | — |
magento/module-sales Version ^103.0 | — | — |
magento/module-store Version ^101.1 | — | — |
magento/module-config Version ^101.2 | — | — |
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.