The MIT declaration, short README, and organization-owned repository provide basic transparency. Its tiny scope limits exposure, but consumers should treat it as effectively unmaintained.
45%
Total Score
50
100
75
75
The latest release was published in August 2015, with no releases in the last 12 months. That long release gap is a substantial abandonment concern despite eight historical releases.
The repository recorded zero commits and zero active maintainers in the last 3 months, consistent with the package having received no recent maintenance.
The repository name does not match the package name and its README does not mention the package. Because this is not explained by a clear monorepo relationship, package ownership is less transparent.
Composer is used for builds, which supports reproducible project structure, but no security scanning tools were detected. The missing scanning is a modest hygiene gap.
The repository has no security policy. This is a transparency and vulnerability-reporting gap, though it is secondary to the package's prolonged inactivity.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
doctrine/dbal Version * | — | — |
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.