Clear documentation, a matching source repository, and an organization-backed project reduce adoption uncertainty. Maintenance has been quiet recently, and the repository has no security policy or automated security scanning.
72%
Total Score
88
100
89
75
The project has existed since October 2018 with 13 releases, but only one release appeared in the last 12 months, indicating a modest and slowing release cadence.
The repository recorded zero commits and zero active maintainers in the last three months, which is a meaningful maintenance warning despite the recent release.
Composer build tooling is present, but no security scanning tools were detected, leaving a modest gap in ongoing project hygiene.
The repository has no SECURITY.md or other security policy, reducing transparency about vulnerability reporting for a plugin that runs inside a CMS.
No GitHub Actions workflows were present, so there are no workflow findings; this also means the repository provides no automated workflow-based security or release checks to assess.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
craftcms/cms Version ^5.0.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.