The project is newly published, so its long-term maintenance record is not established. It has repository tests, a substantial README, a changelog, and read-only workflow permissions, but all 11 workflow actions are unpinned and no security policy is provided.
68%
Total Score
50
100
88
75
The package and repository are owned by the same individual account, providing clear ownership but no organizational backing to demonstrate broader maintenance capacity.
The package was first released today and has four releases in the same day, so there is not yet enough history to demonstrate sustained maintenance. This is an early-stage caution rather than evidence of abandonment.
No commits and no active maintainers were recorded in the last three months, but the repository was only created today and was just updated. This leaves long-term maintenance unproven rather than showing a clear collapse.
The repository uses Composer build tooling, but no security scanning tool was detected. The missing scanning is a modest transparency and maintenance gap for a package handling live content editing.
The repository has no security policy, leaving no documented channel or process for reporting vulnerabilities. This is a transparency gap, not evidence that the package is unsafe.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
statamic/cms Version ^6.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.