Clear licensing, tests, release notes, and a small dependency footprint support dependable use. Ownership continuity merits attention because recent work is concentrated in one contributor, while workflow references are unpinned.
78%
Total Score
83
100
88
67
The package has 31 releases over 372 days and a release within the assessed period, though only two releases occurred in the last 12 months and the reported median interval is zero days.
All 14 recent commits came from one contributor, giving the project a concentrated maintenance base. Organization backing provides some handoff capacity, but no second contributor was active in the measured period.
The project uses Composer and Phing for builds, which supports repeatable packaging, but no security-scanning tools were detected.
The linked repository has no security policy. This is a transparency gap for reporting and handling vulnerabilities, although it does not by itself indicate abandonment.
Both workflows were analyzed without audit findings or untrusted execution sinks, but both action references are unpinned and one workflow grants top-level write permissions. These are workflow hygiene concerns rather than a severe risk without an untrusted trigger.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
composer/installers Version ~1.0 | — | — |
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.