The package includes tests, a README, and a small dependency set, but it has no security scanning or security policy. Its organization-backed repository is not archived, though the very small release history and absent recent commit activity leave maintenance uncertain.
42%
Total Score
50
100
71
83
Only one release exists, published in July 2016, with no releases in the last 12 months. This is strong evidence of a neglected release line and outweighs the otherwise non-deprecated registry status.
There were zero commits and zero active maintainers in the last three months. Combined with the 2016-only release history, this materially raises abandonment and maintenance risk.
There was no new issue or pull request activity in the last month, while two issues and eight pull requests remain open. This is consistent with limited current maintenance capacity.
Composer is used for the build, but no security scanning tools are configured. The missing scanning is a hygiene gap, not a severe risk by itself.
The repository has no security policy, leaving vulnerability reporting and response expectations undocumented. This lowers transparency but does not alone make the release unfit.
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.