Documentation, tests, and release notes make integration and updates easier. The organization-backed project has no security policy, all eight workflow actions are unpinned, and recent commits come from one contributor, so maintenance resilience is limited.
78%
Total Score
83
88
75
All two recent commits came from one contributor. Organization backing provides some handoff capacity, but no second active contributor is shown, leaving maintenance concentrated.
The repository name does not match the package name and its README does not mention the package, so the linkage is less transparent even though the repository otherwise appears purpose-specific.
Composer build tooling is present, but no security scanning tool was detected, leaving automated security coverage unclear.
The repository has no published security policy, reducing transparency about vulnerability reporting and response.
All three workflows were analyzed without high-severity findings or untrusted-code sinks, but all eight action references are unpinned, weakening build reproducibility and update control.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
psr/log Version ^2.0 || ^3.0 | — | — |
twig/twig Version ^2.0 || ^3.0 | — | — |
doctrine/orm Version ^2.8 || ^3.0 | — | — |
symfony/lock Version ^6.4 || ^7.3 || ^8.0 | — | — |
symfony/yaml Version ^6.4 || ^7.3 || ^8.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.