Recent releases and an organization-backed, non-archived repository provide useful continuity. The release notes and repository changelog help, but workflow dependency pinning and missing security scanning leave modest hygiene concerns.
64%
Total Score
50
100
88
67
The repository recorded zero commits and zero active maintainers in the last three months, despite a recent package release. This is the strongest maintenance concern and may indicate work is currently paused or release-only.
The manifest declares a proprietary license, and LICENSE.md exists in both the package and repository. The release is therefore licensed, though proprietary terms may restrict use compared with common open-source licenses.
Composer build tooling is present, but no security scanning tools are configured. That is a modest transparency and maintenance gap, not evidence that the package is unsafe.
The repository has no security policy. This makes vulnerability reporting and response expectations less clear for adopters.
The single workflow was fully analyzed with no dangerous triggers, sinks, or audit findings, and it scopes permissions at job level. Its one action reference is unpinned, leaving a limited reproducibility and workflow supply-chain hygiene gap.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
craftcms/cms Version ^4.0.0 || ^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.