Its README, matching repository, GPL-3.0 license, and simple Composer setup make the package transparent to inspect. There is no security policy or automated security scanning, so maintenance depends heavily on the original author.
40%
Total Score
0
100
67
75
This is the only release, published nearly five years ago, with no releases in the last 12 months. That is strong evidence of an unmaintained dependency.
The repository recorded zero commits and zero active maintainers in the last three months, consistent with the long release gap and increasing abandonment risk.
Composer is used for the build, but no security-scanning tool is configured. The absence of scanning is a modest repository hygiene gap rather than evidence of unsafe code.
The repository is not archived, which leaves a path for future maintenance, but its last push was nearly five years ago and does not offset the inactive history.
No security policy is present, reducing transparency about how vulnerabilities should be reported. This matters more for a module that injects content into storefront output.
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.