Documentation, licensing, and release notes are in place. The small dependency surface and organization-owned repository help, but this two-release package has seen no recent commits and has not been released since November 2015.
45%
Total Score
50
100
75
50
Only two releases exist, with none in the last 12 months; the latest release was in November 2015, more than 10 years ago. This strongly raises abandonment risk.
There were no commits or active maintainers in the last three months. Combined with the last registry release being in 2015, this is strong evidence that maintenance has stopped.
Composer build tooling is present, but no security scanning tooling was detected. This is a modest transparency and maintenance gap, not a standalone severe risk.
The repository has no security policy, leaving vulnerability reporting and response expectations undocumented. The package's long inactivity makes this gap more relevant.
The release is a non-stable 0.x version, which limits maturity confidence, although it is not marked as a prerelease.
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.