The MIT declaration, README, tests, and Composer build support basic transparency and use. Its one-person ownership and lack of security scanning leave limited visible support capacity.
52%
Total Score
38
100
81
83
The latest release was published in June 2018, about 8 years ago, with no releases in the last 12 months. This is strong evidence of stale maintenance for a dependency whose API may need ongoing compatibility fixes.
The repository recorded zero commits and zero active maintainers in the last three months. Combined with the old latest release, this materially increases the risk that fixes and compatibility updates will not arrive.
Only one registry account has publish access, and the project backing identifies an individual repository owner rather than an organization. That leaves limited visible publishing redundancy if the maintainer becomes unavailable.
The registry namespace is associated with an individual repository owner, not an organization-backed source project. That provides less visible institutional continuity than organizational backing.
There are three open issues and two open pull requests, but no new or closed issues and no new or merged pull requests in the last month. This indicates little current project interaction.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
guzzlehttp/guzzle Version ~5.3.1|~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.