The small runtime dependency set and complete source tree make integration straightforward. The project has working tests, release notes, and organizational backing, though recent commit activity is quiet and repository security tooling is limited.
76%
Total Score
75
100
88
83
The package has existed for roughly 9 years with four releases, but only one release in the last 12 months and a median interval of about 2 years 2 months indicate a slow maintenance cadence. The recent 1.0.2 release partly offsets that concern.
There were no commits and no active maintainers in the last 3 months. That is a maintenance concern, although the package had a recent release and repository push.
Composer and Phing build tooling are present, but no security scanning tools were detected. This is a modest transparency and hygiene gap rather than a severe risk.
The repository has no security policy, leaving vulnerability reporting and response expectations undocumented. The package's tests and recent release provide some compensating project evidence, but not a replacement for a policy.
The single workflow was fully analyzed with no dangerous triggers, untrusted checkouts, script injection, or audit findings. Its one action use is unpinned, and it has no top-level permissions block, so workflow hygiene is only mildly limited.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
composer/installers Version ^1.0 || ^2.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.