Tools for working with DBAL in Symfony applications
73%
Total Score
caution
Usable with caveats: recent source activity is thin despite a steady release cadence.
All recent commits came from one contributor, giving the project a narrow recent contributor base. Organization ownership provides some handoff capacity, but no second recent contributor is shown.
Only one commit was recorded in the last three months from one active maintainer. That is thin recent development activity, even though the current release history shows continued publishing.
Composer build tooling is present, but no security-scanning tool was detected. The missing scanner is a modest transparency and maintenance gap rather than evidence of unsafe behavior.
The repository has no security policy. For a database tooling library, this leaves vulnerability-reporting expectations unclear and modestly reduces project transparency.
The single workflow was fully analyzed with no injection or high-confidence audit findings, and it does not grant top-level write permissions. However, all 3 action references are unpinned, which leaves avoidable workflow supply-chain drift.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
doctrine/dbal Version ^4.4 | — | — |
symfony/config Version ^7.4 || ^8.0 | — | — |
symfony/console Version ^7.4 || ^8.0 | — | — |
symfony/validator Version ^7.4 || ^8.0 | — | — |
symfony/http-kernel Version ^7.4 || ^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.