The package is clearly documented, licensed, and has a matching source repository with a release note. Its single-release history and complete lack of recent commits make long-term compatibility and support uncertain.
45%
Total Score
33
100
75
75
There has been only one release, published over five years ago, with no releases in the last 12 months. This is strong evidence of an abandoned or unmaintained dependency.
The repository recorded zero commits and zero active maintainers in the last three months. Combined with the one-release history, this materially increases abandonment risk.
Only one registry publishing account is listed. This is a modest resilience concern for an individually owned project, especially alongside the lack of recent activity.
The package and repository are owned by the same individual account, confirming direct ownership but offering no organizational backing to compensate for the thin maintainer base.
The repository uses Composer for builds, but no security-scanning tools are configured. This is a hygiene gap, not evidence that the package is unsafe on its own.
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.