Asset Health & Safe Cleanup for Craft CMS. Know what's safe to review before you clean.
64%
Total Score
caution
A first-day release has solid documentation and tests, but no maintenance track record or security tooling yet.
One individual has registry publishing access, and the project backing identifies the repository owner as a user rather than an organization. This creates a thin support base for a package intended for production CMS use.
The repository is owned by the same individual namespace as the package, providing consistent ownership context. The user-owned backing does not provide the redundancy of an organization-backed project.
This is the first release, published 0 days ago, with only one release recorded. That is not evidence of abandonment, but it provides no track record for release continuity.
The repository has 0 commits and 0 active maintainers in the last 3 months. Because the package itself is 0 days old, this mainly reflects limited history rather than demonstrated abandonment, but ongoing maintenance is unproven.
Composer is used as a build tool, which fits the package ecosystem. No security scanning tools are configured, leaving a modest transparency and maintenance gap.
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.