A clear README, MIT license, bounded dependencies, and release notes make adoption easier. There is no security policy or automated security scanning, so maintenance depends heavily on one person.
67%
Total Score
50
100
94
83
Registry publishing is controlled by one person. That is consistent with the repository being user-owned, but it leaves the project with a thin visible maintainer base.
The repository had zero commits and zero active maintainers in the preceding 3 months. The recent release partly offsets this, but the lack of ongoing activity raises maintenance uncertainty.
Composer build tooling is present, but no security scanning tools were detected, leaving a security-maintenance gap.
The repository has no security policy. This weakens vulnerability-reporting transparency, although it does not by itself indicate abandonment.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
statamic/cms Version ^6.3 | — | — |
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.