Tests, a clear README, licensing, and no install-time scripts reduce adoption friction. The project has little visible community support and lacks a security policy. Pin CI actions before relying on its build automation.
58%
Total Score
75
100
78
67
The latest release was published in June 2022, with no releases in the last 12 months and only three releases overall. This materially lowers confidence in ongoing maintenance, although the linked repository was pushed more recently.
The repository recorded no commits and no active maintainers in the last three months. This weakens evidence of current maintenance, even though a recent push shows it is not fully abandoned.
The repository has zero stars and two forks, indicating a very small public user base. Popularity is supporting evidence only, but this provides little external reassurance for a long-lived dependency.
The project uses Task and Composer build tooling, but no security scanning tools were detected. The missing scanning layer is a modest transparency and maintenance concern.
No repository security policy was found. For a small database-oriented library this is a transparency gap, though it is not severe on its own.
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.