The repository is small and maintained by one person, with no security policy and unpinned workflow actions. A clear MIT license, repository tests, and a matching source tree provide useful transparency.
62%
Total Score
50
100
88
75
Registry publishing is handled by one person. The matching user-owned repository makes this understandable, but it still leaves a thin maintainer base if that person becomes unavailable.
The latest release was in December 2022, with no releases in the last 12 months. That is a meaningful maintenance concern for a package developers may depend on.
There were no commits and no active maintainers in the last three months. Combined with the stale release history, this raises abandonment risk.
The repository uses Composer, but no security scanning tools were detected. This is a modest transparency and maintenance gap rather than a severe risk.
No security policy is present in the repository, leaving vulnerability reporting and response expectations undocumented.
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.