The source tree is small and the package has a README, an explicit Apache-2.0 license, and no install-time scripts. It has no security policy or scanning, and support rests with one maintainer. Pin this release only with a clear fallback plan.
32%
Total Score
25
75
75
The package has only one release, published in February 2019, with no releases in the last 12 months. This is strong evidence of abandonment for a database library, though the repository is not archived.
The repository recorded zero commits and zero active maintainers in the last three months, consistent with the package's long release inactivity. No newer activity is provided to offset that concern.
Registry publishing access is held by one maintainer. For a user-owned project this is a thin support base, especially alongside the absence of recent commit activity.
Composer is used for the build, but no security-scanning tools are configured. The missing scanning reduces assurance for a dependency handling database connections and caching.
The repository has no security policy, so there is no documented process for reporting or handling vulnerabilities. This is a transparency and maintenance gap, not evidence of malicious behavior.
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.