The MIT license, matching repository, clear README, and organization ownership provide useful transparency. Its small dependency set and lack of install scripts reduce integration risk, but ongoing maintenance should be verified before relying on it for important sites.
58%
Total Score
50
100
71
75
The repository recorded zero commits and zero active maintainers during the last three months. Combined with the short release burst, this is the strongest evidence of currently weak maintenance.
All five releases were published within two days, then no newer release appeared during the package's 285-day lifetime. That suggests a fast initial push without evidence of sustained release maintenance.
There are no open issues or pull requests and no recent issue or pull-request activity. This is not harmful by itself, but it provides no evidence of an active user or maintainer feedback loop.
The repository has two stars and no forks or watchers. Popularity is only supporting evidence, so this modest reach does not materially outweigh the maintenance findings.
Composer is used for build and dependency tooling, which fits the package ecosystem. No security-scanning tools are present, a modest transparency and hygiene gap for a package that connects to multiple AI providers.
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.