The client has a short README, no tests, and no security scanning, which leaves integration and maintenance practices lightly documented. Organization backing, a current stable release, and release notes provide useful counterweight.
65%
Total Score
75
81
83
The artifact includes a README and this exact version has GitHub release notes describing its changes. The absence of tests and a changelog in the published artifact is normal packaging practice, while the brief README limits consumer guidance.
The package has only 4 releases since December 2022 and just 1 release in the last 12 months, indicating a modest maintenance track record. The latest release is current, so this is a concern rather than abandonment evidence.
The repository recorded 0 commits and 0 active maintainers in the last 3 months. This may reflect the recent release timing, but it still provides weak evidence of ongoing maintenance capacity.
The project uses Composer, but no security scanning tools were detected. For an API client this is a meaningful repository hygiene gap, though it is not evidence that the package is unsafe.
The repository has no security policy. This reduces transparency for reporting and handling vulnerabilities, although the small project scope and organization backing partly offset the gap.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
guzzlehttp/guzzle Version ^7.0 || ^8.0 | — | — |
symfony/http-foundation Version >=4.4 | — | — |
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.