The MIT license and stable v3.0 release are reassuring. No commits were recorded in the last three months, and the repository has no security policy, making future maintenance less certain.
55%
Total Score
50
100
86
83
There have been only three releases over roughly two years, with one release in the last 12 months and a median interval of about 331 days. This indicates a slow maintenance cadence, though not abandonment by itself.
The repository recorded zero commits and zero active maintainers in the last three months. Although it was pushed at the latest release, the recent inactivity lowers confidence that fixes will arrive promptly.
The repository uses Composer for its build process, but no security scanning tools were detected. The missing scanning is a hygiene gap, while Composer provides basic build structure.
No security policy was found in the repository. For a Symfony integration package, this leaves the process for reporting and handling vulnerabilities unclear.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
symfony/config Version 5.*|6.*|7.*|8.* | — | — |
symfony/http-kernel Version 5.*|6.*|7.*|8.* | — | — |
symfony/dependency-injection Version 5.*|6.*|7.*|8.* | — | — |
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.