Tests, a useful README, and a small dependency set improve adoption confidence. The organization-backed repository remains identifiable, but its maintenance and documentation safeguards are thin.
57%
Total Score
67
100
81
75
No declared license, license file, or repository license file was detected. This creates a real legal and transparency concern for adoption.
The package has had no release in about three years, with zero releases in the last 12 months. That is meaningful abandonment risk for a library dependency.
There were no commits and no active maintainers in the last three months. Combined with the long release gap, this indicates substantially reduced maintenance capacity.
There were no new or closed issues or pull requests in the last month, while two pull requests remain open. This is consistent with limited recent project activity.
Composer build tooling is present, but no security scanning tools were detected. For a library that handles service integration, this is a modest repository hygiene gap.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
guzzlehttp/guzzle Version ^6.3 || ^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.