The MIT license, tests, compact file tree, and clear README make the client straightforward to inspect and integrate. The missing security policy and limited community activity leave maintenance responsibility uncertain.
44%
Total Score
25
75
88
The latest release was in January 2016, and there have been no releases in about ten years. That long release gap is strong evidence of abandonment risk for a dependency.
The repository recorded zero commits and zero active maintainers in the last three months, and its last push was over seven years ago. The non-archived status does not compensate for this sustained inactivity.
There were no new or closed issues or pull requests in the last month, while three pull requests remain open. This indicates little current maintenance or review activity.
The linked repository name does not match the package and its README does not mention the package. The organization-owned repository provides some context, but the package-to-repository relationship is not transparently established.
The repository has no security policy, leaving no documented process for reporting or handling vulnerabilities. This is a maintenance and transparency gap, though it is not evidence of malicious behavior.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
guzzlehttp/guzzle Version 6.* | — | — |
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.