Clear documentation, release notes, and a matching organization-owned repository make installation straightforward. The small project has no recent commits, and all six CI actions are unpinned, reducing confidence in ongoing maintenance and build reproducibility.
61%
Total Score
83
100
88
67
The package has six releases, but none in the last 12 months and the latest was about 19 months ago. Earlier release activity provides some maturity, but the current pause lowers maintenance confidence.
The repository recorded zero commits and zero active maintainers in the last three months. Together with the absence of releases in the last year, this is a meaningful maintenance concern.
Composer build tooling is present, but no security scanning tools were detected. The missing scanning is a modest transparency and hygiene gap, not evidence of an unsafe release by itself.
The repository has no security policy. That makes vulnerability reporting less transparent, although the package's small scope and other repository documentation partly reduce the impact.
The sole workflow was fully analyzed with no injection or high-severity findings, but all six action references are unpinned. That weakens build reproducibility and supply-chain hygiene without making the release unfit on its own.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
craftcms/cms Version ^4.0.0|^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.