The package includes a substantial README, tests, and matching MIT licensing. Its single-person ownership and absent security policy reduce confidence for a Laravel integration; pin v1.2 if adopting.
62%
Total Score
50
88
50
One registry maintainer is consistent with a user-owned project, but it leaves little visible publishing redundancy if the maintainer becomes unavailable.
The package is about 1 year 5 months old, but its three releases were concentrated in the first week and there were no releases in the last 12 months. This indicates stalled maintenance despite the initial release activity.
The repository recorded zero commits and zero active maintainers in the last three months, consistent with the absence of recent releases. That weakens confidence that compatibility issues will be addressed.
Composer build tooling is present, but no security scanning tools were detected. This is a modest transparency and maintenance gap, not evidence that the package is unsafe.
The repository has no security policy, so there is no documented process for reporting or handling vulnerabilities in this Laravel integration.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
doctrine/dbal Version ^4.3 | — | — |
laravel/framework Version ^12.0 | — | — |
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.