Clear documentation and a recent release history add confidence. The project is actively changing, but one contributor carries all recent commits and workflow references are not pinned. A missing security policy leaves a smaller transparency gap.
68%
Total Score
75
100
94
75
All 77 recent commits came from one contributor, so maintenance depends heavily on a single person despite the strong activity level.
Composer build tooling is present, but no security scanning tools were detected, leaving a modest verification gap.
The repository has no security policy, which reduces transparency for reporting and handling vulnerabilities.
Both workflows were analyzed without untrusted checkouts or script injection, but all 11 action references are unpinned and one workflow has top-level write permissions. The only audit finding is low-confidence cache-poisoning hygiene, so this is a caution rather than a severe workflow risk.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
getkirby/composer-installer Version ^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.