Usable with caveats: the package is clearly documented, tested, licensed, and not deprecated or archived. However, it has had no release in the last 12 months, no recent commits, and relies on a single maintainer, so maintenance continuity is uncertain.
68%
Total Score
63
100
81
80
Only one account has registry publishing access. The repository is user-owned rather than organization-owned, so the narrow maintainer base creates a real continuity risk.
The registry namespace and repository owner align around the same individual, but the project is user-backed rather than organization-backed. That is consistent ownership, with limited institutional continuity.
The package has existed since 2014 and has nine releases, but it has had no release in the last 12 months. The long median interval of about 317 days suggests slow maintenance, though not abandonment by itself.
The repository recorded zero commits and zero active maintainers over the last three months. Combined with no registry release in the last 12 months, this lowers confidence in ongoing maintenance.
Composer build tooling is present, but no security scanning tool was detected. For this small library that is a transparency gap rather than evidence of an unsafe release.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
doctrine/dbal Version ^3.3 || ^4 | — | — |
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.