Healthy and reasonable to adopt, with routine project-level caveats. It has rapid recent releases, active development, strong documentation, and organization backing; the main concerns are that one contributor made all recent commits and the repository lacks a security policy and explicit workflow token permissions.
84%
Total Score
83
100
89
67
All 73 recent commits came from one contributor, creating a real continuity risk; organization ownership partly compensates because maintenance can potentially be handed off.
The repository has zero stars, forks, and watchers. This is weak supporting evidence, but popularity is not decisive and the package is demonstrably active through releases and commits.
Composer build tooling is present, but no security scanning tools were detected; this is a modest transparency and assurance gap for a maintained plugin.
The repository has no security policy, leaving vulnerability reporting and response expectations undocumented.
The only workflow lacks top-level token permissions. No write permissions were detected, but explicitly restricting the workflow would provide stronger CI security hygiene.
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.