The project has no security policy or security-scanning tooling, and both workflow actions are unpinned. Organization backing, tests, licensing, and a clear README provide useful counterweight.
67%
Total Score
75
94
50
The repository recorded zero commits and zero active maintainers in the last three months. This is a meaningful maintenance concern, although the recent push and annual release history provide some counterweight.
Composer is used for builds, but no security-scanning tools are configured. The missing automated security coverage is a modest transparency and maintenance gap.
The repository has no security policy. That leaves vulnerability-reporting and response expectations unclear for a package used in development workflows.
The only workflow was fully analyzed and has no untrusted checkout or script-injection trigger, but both action references are unpinned and the auditor found a high-confidence template-injection pattern. These are workflow hygiene concerns rather than a standalone severe dependency risk.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
symfony/yaml Version ~6.3 | — | — |
symfony/finder Version ~6.3 | — | — |
symfony/console Version ~6.3 | — | — |
battye/php-array-parser 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.