The last three months show three commits from one contributor, and the workflows leave actions unpinned. Documentation, licensing, and organization ownership provide useful support for adoption.
76%
Total Score
83
94
67
All three recent commits came from one contributor, concentrating current activity in a single person. Organizational backing partly reduces handoff risk, but the recent contributor base remains narrow.
Composer and Phing build tooling are present, but no security scanning tools were detected. The missing scanning is a modest transparency and hygiene gap rather than evidence of abandonment.
The repository has no security policy, leaving vulnerability reporting expectations unspecified. This is a minor transparency gap for a maintained extension.
Both workflows were analyzed cleanly with no dangerous triggers, untrusted checkouts, script injection, or audit findings. However, both action references are unpinned and one workflow grants top-level write access, creating a moderate workflow-hygiene concern.
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.