The repository remains connected, tested, and recently pushed, while its small user-maintainer base limits resilience. The release workflow uses broad write access and unpinned actions, though its low-confidence cache warning is only a hygiene concern.
65%
Total Score
50
100
89
67
The package and repository are owned by the same individual account. A single-person project is plausible here, but it offers less organizational continuity than backed projects.
The package has 22 releases since August 2021, but none in the last three years; the latest registry release was in November 2023. This is a meaningful maintenance concern, although the repository was pushed in April 2025.
Composer build tooling is present, but no security scanning tool was detected. That is a modest transparency and hygiene gap, not evidence of abandonment by itself.
The repository has no security policy, leaving vulnerability-reporting expectations unclear. This is a transparency gap for a maintained package, but not a severe adoption blocker alone.
The sole workflow gives every job top-level write permissions and all three action references are unpinned. The audit also found a low-confidence cache-poisoning pattern; because it is low confidence and no untrusted trigger or checkout was found, this remains workflow hygiene rather than a severe risk.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
getkirby/composer-installer Version ^1.2 | — | — |
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.