Repository tests and release notes support a maintainable codebase, and organization backing adds continuity. The lack of a security policy leaves maintenance transparency weaker.
58%
Total Score
75
92
75
Only two releases were published, both about 21 months ago, with none in the last 12 months. This is a substantial maintenance concern for a dependency, despite the package reaching a stable major version.
The repository recorded no commits and no active maintainers in the last three months. This corroborates the aging release history and raises abandonment risk.
No security policy is present in the repository. That weakens vulnerability-reporting transparency, though it is a secondary concern compared with the maintenance signals.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
guzzlehttp/guzzle Version ^7.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.