The stable release history and focused package structure support adoption. Repository activity is very light and entirely concentrated in one contributor, while security scanning and a security policy are absent.
72%
Total Score
50
100
93
67
All recent commits come from one contributor, giving the project a single-person bus factor. No organizational backing is shown to compensate for that concentration.
Only one commit was recorded in the last 3 months, with one active maintainer. The recent repository push is reassuring, but the low activity leaves maintenance capacity uncertain.
Composer build tooling is present, but no security-scanning tooling was detected. This is a maintenance and transparency gap rather than a severe risk by itself.
The repository has no security policy. For an administrative Magento extension, this weakens the published process for reporting and handling security issues.
No GitHub Actions workflows were present, so there are no workflow findings or exposed workflow permissions to penalize. This provides no CI or automated security assurance, but the absence of workflows is not itself a dangerous configuration.
We didn't find any vulnerabilities for this package.
No maintainer information available.
No direct dependencies.
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.