Common exceptions, attributes, value resolvers and utilities for Symfony applications
78%
Total Score
healthy
Active releases and solid project structure outweigh single-contributor and limited security-process concerns.
One contributor made all 11 commits in the last 3 months, creating a real continuity risk. Organization ownership provides some handoff capacity, so this is a caution rather than a severe risk.
There were no new or closed issues or pull requests in the last month, so there is little evidence of community support or review activity; open counts are unknown.
The repository has zero stars, forks, and watchers. Popularity is only supporting evidence, but these counts provide no external adoption signal for this young project.
Composer and Make are used as build tools, but no security-scanning tooling is reported. The missing scanning process is a modest transparency and maintenance concern, not evidence of unsafe code.
The repository has no security policy, leaving the reporting and response process unclear for a package used in application infrastructure.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
symfony/uid Version ^7.0 || ^8.0 | — | — |
psr/container Version ^1.1 || ^2.0 | — | — |
symfony/validator Version ^7.0 || ^8.0 | — | — |
symfony/http-kernel Version ^7.0 || ^8.0 | — | — |
doctrine/persistence Version ^3.0 || ^4.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.