A single contributor handles all recent commits, and the repository has no security policy or scanning tools. Clear licensing, release notes, stable versioning, and organization backing improve maintainability.
82%
Total Score
83
100
94
67
All 26 recent commits came from one contributor, creating a meaningful continuity risk despite the repository's organization ownership.
The project uses Composer, but no security-scanning tools were detected; the build tooling is present while security automation is limited.
The repository has no security policy, leaving vulnerability-reporting and response expectations undocumented.
No GitHub Actions workflows were present to audit, so there are no workflow findings, but there is also no CI or workflow evidence supporting build and release hygiene.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
guzzlehttp/guzzle Version ^7.0 || ^8.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.