Healthy and suitable to use, with one meaningful maintenance risk: all recent repository work comes from a single contributor. It has frequent stable releases, an active non-archived organization-backed repository, release notes, tests in the repository, and no install-time scripts.
82%
Total Score
88
100
94
75
One contributor made all 93 commits in the last 3 months, creating a genuine continuity risk. Organization backing provides some capacity to hand off maintenance, but no second active contributor is evidenced here.
Composer is used for builds, which supports a defined build process, but no security scanning tools were detected. The lack of scanning is a modest transparency gap rather than evidence of abandonment.
The repository has no security policy, leaving vulnerability-reporting expectations undocumented. This is a transparency gap, although the active repository and controlled workflow reduce its overall weight.
The release workflow declares top-level write permissions. This expands the potential impact of a workflow compromise, though the separate workflow analysis found no dangerous trigger or checkout pattern.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
getkirby/composer-installer Version ^1 | — | — |
johannschopplich/kirby-tools-utils Version ^0.1.3 | — | — |
johannschopplich/kirby-tools-licensing Version ^0.9 | — | — |
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.