A two-person contributor base and no dedicated security tooling or policy leave some operational risk. The organization backing, strong documentation and tests, regular releases, and clean workflow audit materially offset those concerns.
88%
Total Score
83
100
94
83
Two contributors were active recently, but one authored 90% of the 10 commits; this concentration leaves a meaningful handoff risk despite the organization's backing.
Composer build tooling is present, but no security scanning tools were detected, leaving security-quality automation less visible than the project's general build process.
The repository has no security policy, which makes vulnerability reporting and response expectations less transparent for adopters.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
guzzlehttp/guzzle Version ^7.5|^8.0 | — | — |
laravel/framework Version ^10.15|^11|^12.0|^13.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.