The client is small and lightly adopted, with no security scanning or published security policy. Its clear README, license, matching repository, and exact-version release notes improve transparency but do not offset the long maintenance gap.
42%
Total Score
50
72
75
The latest release was in April 2019, with no releases in the last 12 months and only five releases overall. This is strong evidence of abandonment risk despite the historical release record.
The repository recorded zero commits and zero active maintainers in the last three months, consistent with the release history and indicating no current maintenance capacity.
The repository has zero stars, two forks, and one watcher. Low popularity is only supporting evidence, but it provides little community support to compensate for inactivity.
Composer build tooling is present, but no security scanning tools were detected. That leaves dependency and source-security checks less transparent.
The repository has no security policy, so users have no stated channel or process for reporting vulnerabilities in this API client.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
guzzlehttp/guzzle Version ~6.0 | — | — |
guzzlehttp/guzzle-services Version 1.1.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.