The small contributor base and missing security policy leave limited evidence of ongoing care. MIT licensing, tests, documentation, and a simple dependency profile are solid foundations.
55%
Total Score
50
100
80
75
The latest release was in October 2019, nearly seven years ago, with no releases in the last 12 months. This is a substantial maintenance concern, though the package has a stable release history rather than erratic publishing.
The repository recorded no commits and no active maintainers in the last three months, consistent with a project that has received little recent care. The repository is not archived, which reduces but does not remove the concern.
There were no new or closed issues or pull requests in the last month, while three issues and one pull request remain open. This provides little evidence of active maintenance.
Composer build tooling is present, but no security scanning tools were detected. The missing scanning is a modest hygiene gap rather than evidence that the release is unsafe.
The repository has no security policy, leaving vulnerability reporting and response expectations undocumented. This is a transparency gap for a library making HTTP API requests.
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.