Healthy and suitable to depend on, with strong release discipline, documentation, tests, and an active organization-backed repository. Review its limited recent commit activity and incomplete GitHub security hardening before adopting it in a high-assurance environment.
82%
Total Score
67
94
80
All recent commits came from one contributor, which creates concentration risk. The organization-owned repository provides some handoff capacity, so this is a caution rather than a severe dependency risk.
Only one commit from one active maintainer was observed in the last three months. Although the recent release indicates the project is not abandoned, the low short-term activity is a maintenance concern.
Composer is used as the build tool, but no security scanning tool was detected. The standard build tooling is appropriate, while the missing security automation leaves a modest transparency gap.
The repository has no security policy. That weakens vulnerability-reporting transparency, although it does not by itself indicate abandonment or make the release unfit to use.
Seven workflows omit top-level token permissions and one release workflow grants top-level write access. This is weaker CI permission hygiene and increases operational risk, though the separate workflow analysis found no dangerous workflow patterns.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
magento/framework Version ^103.0.0 | — | — |
magento/module-contact Version ^100.4.0 | — | — |
magento/module-checkout Version ^100.3.0 | — | — |
magento/module-customer Version ^102.0.0|^103.0.0 | — | — |
magento/module-newsletter Version ^100.3.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.