The small dependency set, clear license, and included tests make the code relatively easy to inspect. The README calls it unfinished and unsuitable for production, while its Guzzle 5-era requirements further limit confidence in long-term use.
42%
Total Score
100
50
50
88
The latest release was in June 2015, with no releases in the last 12 months and only four releases overall. This is strong evidence of abandonment for a library intended as a maintained dependency.
The repository is not archived, which is a positive counter-signal, but it was last pushed in March 2017—about 9 years ago—showing that the project is effectively inactive.
The package has only one runtime dependency, keeping the dependency surface small. Its documented Guzzle 5-era requirements are very old, which raises compatibility and maintenance concerns despite the limited count.
The artifact includes a README and tests, which support inspection and basic use. However, the README explicitly says the project is unfinished and should not be used in production, materially reducing adoption confidence.
Composer is used for builds, which fits the package ecosystem. No security scanning tooling is present, leaving a modest supply-chain hygiene gap that adds to the wider maintenance concerns.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
guzzlehttp/guzzle-services Version 0.5.* | — | — |
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.