Tests, a README, and a clear MIT license make the package easy to inspect. Its small, matching source project and single runtime dependency keep adoption straightforward, but provide limited assurance beyond the original release.
43%
Total Score
50
100
81
83
The package has only two releases, with the latest published in January 2015 and none in roughly 11 years. This is strong evidence of abandonment risk for a dependency that may need compatibility fixes.
The repository recorded zero commits and zero active maintainers in the last three months, consistent with the release history showing no activity since January 2015.
There were no new or closed issues or pull requests in the last month, and no open work is visible. This supports the conclusion that the project is inactive, though it is secondary to the long release gap.
Composer build tooling is present, but no security-scanning tools were detected. For a small, old package this is a modest transparency and maintenance gap rather than a standalone disqualifier.
The repository has no security policy. That weakens the project's vulnerability-reporting transparency, although the package's small scope and otherwise inspectable source reduce the impact.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
guzzlehttp/guzzle Version 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.