The project has a clear README, a matching source repository, a permissive license, and a small dependency footprint. Recent repository inactivity, no security policy, and one unpinned workflow action leave meaningful maintenance and build-hygiene concerns.
72%
Total Score
88
100
94
83
The repository recorded 0 commits and 0 active maintainers in the last 3 months. The release-time push is compensating evidence, but the absence of broader recent development still lowers confidence in ongoing maintenance.
Composer is used for the build, but no security scanning tools are configured. For a small plugin this is a hygiene gap rather than a severe dependency risk.
The repository has no security policy. This weakens transparency for reporting vulnerabilities, although it does not by itself show that the package is unsafe.
The single workflow was fully analyzed with no audit findings, no untrusted checkout, and no injection sink. Its only action reference is unpinned, which leaves build provenance weaker, while the lack of a top-level permissions block is acceptable on its own.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
getkirby/composer-installer Version ^1.1 | — | — |
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.