Healthy and suitable to use. It has a long release history, a current stable release, active Symfony organization backing, tests in the repository, and recent issue and pull-request activity; recent commits are concentrated in one contributor, so maintenance depth is the main caveat.
82%
Total Score
80
100
94
90
All 3-month commit activity comes from one contributor with a 100% share, creating concentration risk. Symfony organization backing provides some handoff capacity, but no second contributor was active in this period.
Only 1 commit was recorded in the last 3 months from 1 active maintainer, which indicates low recent commit volume; the current release history and substantial issue and pull-request activity partly compensate.
Composer build tooling is present, but no security scanning tools were detected. This is a transparency and defense-in-depth gap, though it is not enough to outweigh the repository's other maintenance evidence.
One workflow declares read-only permissions, while ci.yaml lacks top-level permissions. No workflow requests top-level write access, but the missing explicit declaration is a modest hardening gap.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
symfony/config Version ^7.3 || ^8.0 | — | — |
monolog/monolog Version ^3.12 | — | — |
symfony/http-kernel Version ^7.3 || ^8.0 | — | — |
symfony/monolog-bridge Version ^7.3 || ^8.0 | — | — |
symfony/polyfill-php84 Version ^1.30 | — | — |
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.