The package is small, documented, and has a stable release with minimal runtime dependencies. However, no commits or releases since September 2023, one maintainer, and no security policy or scanning indicate limited ongoing support.
58%
Total Score
50
100
88
83
One registry maintainer creates a thin publishing base and increases continuity risk if that person becomes unavailable. The repository is user-owned, so this is not offset by organization backing.
The package has 8 releases since March 2019, but none in the last 12 months and its latest release was in September 2023. This long pause materially raises maintenance risk.
There were no commits and no active maintainers in the last three months, consistent with the release pause and indicating little current capacity for fixes.
Composer build tooling is present, but no security scanning tools are configured. This is a modest transparency and maintenance gap for a dependency project.
The repository has no security policy, leaving vulnerability reporting and response expectations unspecified. This is a hygiene gap rather than evidence of an unsafe release.
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.