Refuses to publish a Statamic entry that fails the accessibility checks it can actually run.
82%
Total Score
88
100
75
90
The registry namespace and repository are consistently owned by the same individual account. This is independent rather than organizational backing, but the repository has a second active contributor to offset the otherwise narrow ownership structure.
The package is very young at 34 days, although 22 releases in that period show active iteration rather than abandonment. The extremely short median interval suggests a still-forming project and warrants some caution.
The repository has no stars, forks, or watchers, which provides no external adoption evidence; the package's very young age makes this a modest concern rather than a decisive risk.
Composer build tooling is present, but no security scanning tools were detected, leaving a security-maintenance gap that is partly offset by the repository's active tests and CI workflow.
No repository security policy was found, so vulnerability reporting and response expectations are less transparent for consumers.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
statamic/cms Version ^6.27 | — | — |
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.