The package is small and straightforward, with one runtime dependency and four releases in the last year. Documentation, testing, security policy, and recent repository activity are limited, so maintenance risk remains meaningful despite the recent release.
62%
Total Score
75
100
81
67
The package and repository each contain only three files, indicating a very small implementation that is easy to inspect but offers little surrounding project context.
The published artifact has no README, and the repository also reports no tests or changelog. For a library intended to bridge Doctrine DBAL, the lack of consumer documentation and visible validation lowers transparency.
The repository recorded no commits and no active maintainers in the last three months. The recent release partly offsets this, but it leaves current maintenance capacity uncertain.
Composer build tooling is present, but no security-scanning tooling was detected. This is a modest repository-hygiene gap rather than evidence that the release is unsafe.
The repository has no security policy, leaving vulnerability-reporting expectations unclear. This is a transparency concern for a dependency, but not a severe adoption blocker by itself.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
doctrine/dbal Version >= 2.13 | — | — |
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.