The repository has no security scanning, and its only workflow uses an unpinned action. Organization backing, a matching repository, a valid license, and a documented release history provide useful transparency.
58%
Total Score
50
83
75
There were zero commits and zero active maintainers in the last three months, while the last repository push was about nine months ago; this is a meaningful maintenance concern.
The package has six releases, but all were published within its first month and the latest release was about nine months ago, suggesting an unproven maintenance pattern.
Composer build tooling is present, but the repository has no security scanning tools, leaving a notable project-hygiene gap.
The repository has no security policy, which weakens vulnerability-reporting transparency for a package that integrates into Craft CMS projects.
The workflow is fully analyzed and scopes permissions at job level, with no untrusted trigger or injection findings; however, its one action use is unpinned, weakening build reproducibility.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
craftcms/cms Version ^5.0.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.