The MIT license and simple Composer setup make the package easy to evaluate and integrate. Its tiny codebase, absent tests and security policy, and single active contributor leave limited evidence for long-term maintenance.
62%
Total Score
67
100
88
67
The package and repository each contain only five files, including one source file and no test suite. This may be sufficient for a small SDK, but it provides little visible project structure for assessing maturity.
All two recent commits came from one contributor. Organization ownership provides some capacity to hand maintenance off, but no second active contributor is shown, leaving a thin operational safety net.
The repository had two commits in the last three months, so it is not inactive, but the activity is light and provides only modest evidence of ongoing maintenance.
Composer is used as the build tool, which fits the package ecosystem. No security scanning tooling was detected, reducing automated safeguards but not making the package unfit on its own.
The repository has no security policy, leaving no documented process for reporting or handling vulnerabilities. This is a transparency and maintenance gap for a network-facing API SDK.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
guzzlehttp/guzzle Version ^8.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.