The project is only 40 days old, so its longer-term maintenance record is still unproven. It has shipped three stable releases, received recent commits from two contributors, and includes tests, documentation, release notes, and a license.
78%
Total Score
80
100
88
88
Only one account has registry publish access, which creates some publishing concentration. Two active repository contributors provide partial practical compensation, but the project remains primarily dependent on one publisher.
The package is only 40 days old with three releases and a median interval of about 20 days. The recent cadence is encouraging, but there is not yet a long maintenance record.
Two contributors were active in the last three months, although the leading contributor made 75% of commits. The second contributor reduces, but does not eliminate, concentration risk.
Composer build tooling is present, but no security scanning tool was detected. For a young package this is a modest transparency and hygiene gap, not evidence of abandonment.
The repository has no security policy. That weakens the documented process for reporting and handling vulnerabilities, though it does not by itself show unsafe code or poor maintenance.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
craftcms/cms Version ^5.3.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.