Risky to adopt for a new dependency: the package has had no release or repository activity for more than four years. It is clearly identified, MIT-licensed, and backed by a matching organization repository, but its maintenance appears effectively dormant.
45%
Total Score
50
100
71
83
The latest release was published on April 4, 2022, and there have been no releases in the last 12 months despite 16 releases overall. This long period without updates is a substantial abandonment concern.
The repository recorded zero commits and zero active maintainers in the last three months, consistent with the package's prolonged lack of releases. The organization backing does not compensate for the absence of observed maintenance activity.
Composer is used as the build tool, but no security scanning tools are present. The missing scanning is a transparency and maintenance gap, though it is less significant than the package's long inactivity.
The repository is not archived, which avoids the strongest abandonment signal, but its last push was on April 4, 2022. The non-archived status provides only limited reassurance against the observed inactivity.
The repository has no security policy. For an API client this is a genuine disclosure-process gap, but it does not by itself establish that the package is unsafe.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
guzzlehttp/guzzle Version ^6.0 || ^7.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.