The README is short, and there is no security policy or automated security scanning. The MIT license, matching repository, and lack of install scripts reduce adoption friction but do not offset the maintenance risk.
35%
Total Score
25
100
75
75
The latest release was about 10 years ago, with no releases in the last 12 months. The earlier three-release history shows initial activity but no current maintenance.
The repository recorded zero commits and zero active maintainers in the last three months, reinforcing the long release gap and indicating likely abandonment.
Six issues remain open, while no issues or pull requests were closed or merged in the last month. This is weaker evidence than the inactive commit history but adds unresolved-maintenance concern.
Composer build tooling is present, but no security scanning tools are configured. That leaves dependency and repository security checks less transparent.
The repository has no security policy, leaving no documented process for reporting or handling vulnerabilities. This is a transparency gap for a client library that handles API access.
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.