Clear documentation, tests, licensing, and a matching repository improve confidence. Maintenance has gone quiet for three months, while all four workflow actions are unpinned and the project has no security policy.
58%
Total Score
50
50
83
50
Thirty runtime dependencies create a broad dependency surface for a Symfony bundle, increasing transitive maintenance burden even though the dependencies fit the package's stated integrations.
The package has only two releases, both within 11 days, so its maintenance record is still short and provides limited evidence of long-term support.
No commits and no active maintainers were recorded in the last three months, which is a meaningful sign that ongoing maintenance may have slowed.
The repository has zero stars, forks, and watchers; this is weak supporting evidence, but popularity alone does not outweigh the package's documentation and tests.
Composer build tooling is present, but no security-scanning tooling was detected, leaving security hygiene less visible.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
doctrine/orm Version ^3.0 | — | — |
symfony/yaml Version ^7.3 | — | — |
doctrine/dbal Version ^4.0 | — | — |
nesbot/carbon Version ^2.72 || ^3 | — | — |
symfony/config Version ^7.3 | — | — |
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.