The project has 19 open issues, no security policy, and no automated security scanning. Organization backing, tests, release notes, and licensing provide useful transparency.
70%
Total Score
67
88
75
The repository had zero commits and zero active maintainers in the last three months. Although a recent release shows some maintenance, the current source activity is a meaningful abandonment warning.
There are 19 open issues, with no new or closed issues and no pull-request activity in the last month. This suggests limited visible issue follow-through.
The repository name does not match the package name and its README does not mention the package. This weakens confidence that the linked source is specifically the published package, even though organization backing and matching extension content provide some compensation.
Composer build tooling is present, but no security-scanning tool was detected. That is a modest transparency and maintenance gap, not evidence of an unsafe release by itself.
The repository has no security policy. For an extension that handles account credentials and an external REST API, the lack of a documented vulnerability-reporting process is a genuine transparency gap.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
magento/product-community-edition Version ^2.4.4 | — | — |
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.