The package is clearly licensed, documented, and has a focused dependency set with release notes for this version. A single maintainer, no security policy, and an apparently mismatched repository reduce confidence in long-term support.
60%
Total Score
75
100
86
75
The package has existed since December 2017 and has nine releases, but its latest release was about 20 months ago with no releases in the last 12 months. That extended gap lowers confidence in ongoing maintenance.
There were no commits or active maintainers in the three months measured, consistent with the long interval since the last release. This is a meaningful maintenance concern for a package tied to an evolving CMS.
The repository name does not match the package name and its README does not mention the package. That weakens confidence that the linked repository is the canonical source rather than a related or reused repository.
The repository has no security policy. This is a transparency and response-process gap, though it is not by itself evidence that the package is unsafe.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
craftcms/cms Version ^5.0.0-beta.11 | — | — |
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.