Documentation, repository tests, and release notes make integration straightforward. Its small dependency set and MIT licensing help, but the lack of security scanning limits assurance.
58%
Total Score
25
100
81
83
The package has four releases over nearly ten years, with no release in the last 12 months and the latest release in August 2019. This indicates substantial abandonment risk for a maintained SDK.
The repository recorded zero commits and zero active maintainers in the last three months, consistent with the long release gap. No provided activity signal compensates for this lack of ongoing maintenance.
One registry account can publish the package. Because the repository is owned by the same individual, this reflects a thin but coherent maintainer base rather than an unexplained publishing mismatch.
Composer build tooling is present, but no security-scanning tools were detected. The missing scanning is a modest transparency and maintenance concern for a library dependency.
The repository has no security policy, leaving no stated process for reporting or handling vulnerabilities. This is a hygiene gap, but not severe enough to outweigh the package's documentation and licensing.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
guzzlehttp/guzzle Version ~6.2 | — | — |
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.