The project includes tests, recent releases, and active contributions from two maintainers within an organization-backed repository. Workflow permissions, mostly unpinned actions, template-injection findings, and the lack of security scanning or a security policy leave meaningful hygiene gaps.
76%
Total Score
100
100
94
50
The project uses Composer build tooling, but no security-scanning tool was detected, leaving automated dependency or code scanning coverage unknown.
The repository has no security policy, reducing transparency about how vulnerabilities should be reported and handled.
All six workflows were analyzed, but 15 of 16 action references are unpinned, three workflows grant top-level write permissions, and high-confidence template-injection findings appear in the release workflow. The template-injection findings are workflow hygiene concerns here because no untrusted checkout or script-injection trigger was observed.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
composer/installers 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.