The short README gives consumers little guidance. Two active contributors, regular releases, tests, and organization backing provide meaningful maintenance capacity; the lack of security tooling and policy remains a documentation gap.
84%
Total Score
100
100
86
75
Tests are present in both the package and repository, which supports maintainability. The 18-character README is unusually minimal for a library consumers must integrate, while the absent changelog is normal packaging practice.
Composer build tooling is present, but no security-scanning tools were detected. The missing scanning is a modest transparency and maintenance gap.
The repository has no security policy. This makes vulnerability reporting and response expectations less clear, though it does not by itself show unsafe code.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
guzzlehttp/guzzle Version ^7.4 | — | — |
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.