Clear ownership, a matching repository, a license, and release notes improve transparency. The small user base and absent security policy leave less evidence for long-term support.
60%
Total Score
67
100
88
75
The package has had no release in the last 12 months, and its latest release was over two years ago despite a six-release history. This materially lowers confidence in ongoing maintenance.
There were no commits and no active maintainers in the last three months, consistent with the package's long release gap and raising abandonment risk.
The repository has three open issues but no new or closed issues, pull requests, or merges in the last month. This is a modest sign of limited current engagement.
Composer build tooling is present, but no security scanning tools were detected. That is a meaningful maintenance and transparency gap for an API client.
The repository has no security policy, leaving the project's process for receiving and handling vulnerability reports unspecified.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
guzzlehttp/guzzle Version ^6.0|^7.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.