Recent maintenance is quiet even though the project shipped a current release, and the repository lacks a security policy. Clear licensing, tests in the repository, release notes, and regular recent releases provide useful transparency.
66%
Total Score
67
94
75
There were no commits and no active maintainers in the last 3 months. This is a meaningful maintenance concern, although recent releases partly compensate for it.
No issues or pull requests were created, closed, or merged in the last month, despite 18 open issues and 21 open pull requests, suggesting limited current follow-through.
Composer build tooling is present, but no security-scanning tools were detected; that weakens the project's ongoing security hygiene.
The repository has no security policy. For a maintained database library, this leaves vulnerability reporting and response expectations unclear.
The workflow audit completed cleanly with no dangerous triggers, untrusted checkouts, script injections, or audit findings. However, all 3 action references are unpinned, which is a supply-chain hygiene gap.
We didn't find any vulnerabilities for this package.
No direct dependencies.
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.