The focused codebase has clear documentation, release notes, and organization backing, with only one runtime dependency. Its lack of recent repository activity and security policy leaves maintenance and disclosure coverage weaker than ideal.
60%
Total Score
75
100
88
88
Only two releases exist, both ending in April 2022, with no releases in roughly four years. That is meaningful evidence of a stale release cadence for a dependency, despite the stable version.
The repository recorded zero commits and zero active maintainers in the last three months, consistent with no activity since April 2022. This materially increases abandonment risk.
Composer is used for the build, which fits the package ecosystem, but no security scanning tooling is present. The missing scanning is a hygiene weakness rather than evidence that the release is unfit.
The repository has no security policy, leaving vulnerability reporting and disclosure expectations unclear. This is a transparency gap, though the package is small and has a limited dependency surface.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
craftcms/cms Version ^3.4.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.