The tiny repository and absent security tooling reduce confidence in ongoing support. The MIT license, README, and organization ownership provide useful transparency, but no security policy or scanning is present.
38%
Total Score
0
50
50
Only two releases were published, both in May 2017, with no release in more than nine years. That is strong evidence of abandonment for a dependency still being considered today.
The repository recorded zero commits and zero active maintainers in the last three months, consistent with the long release gap and leaving little evidence of ongoing maintenance.
The repository has only 1 star, 1 fork, and 4 watchers, providing little supporting evidence of broad community adoption or backup maintenance capacity.
Composer build tooling is present, but no security scanning tools were detected. This is a maintenance and transparency gap, though it is less significant than the prolonged inactivity.
No repository security policy was found, so there is no documented process for reporting or handling vulnerabilities in this client library.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
guzzlehttp/guzzle Version ~6.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.