The project is small, with one maintainer, no security policy, and no automated security scanning. It has clear documentation, an MIT license, a stable release, and a recent release history, but the linked repository does not clearly identify this package and has had no commits in three months.
56%
Total Score
50
100
71
75
The repository name does not match the package name and its README does not mention the package, so the source linkage is not clearly established. This creates a meaningful transparency and provenance concern.
The repository recorded 0 commits and 0 active maintainers in the last 3 months. The release pushed at the end of that period shows recent publication activity, but ongoing maintenance is not demonstrated.
The repository has 0 stars, 0 forks, and 1 watcher, providing little external evidence of adoption or review. Popularity is supporting evidence only, so this modestly lowers confidence rather than determining the verdict.
Composer is used for the build, but no security-scanning tools are configured. The missing scanning is a hygiene gap rather than evidence that the package is unsafe.
The repository has no security policy. For a PHP database library, this leaves vulnerability-reporting and maintenance expectations less clear.
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.