Healthy and reasonable to depend on. It has active recent releases, current repository activity from two contributors, tests, documentation, and no deprecation or archived-repository warning; the missing security policy and undeclared workflow permissions are the main caveats.
82%
Total Score
80
100
94
80
Only one registry publishing account is listed, which is a modest publishing-bus-factor concern, but repository activity shows a second active contributor.
The repository is owned by an individual rather than an organization, so the single registry maintainer and small contributor base represent a real continuity consideration.
The repository has no stars, forks, or watchers, so it has little visible community adoption; this is supporting evidence only and is outweighed by active releases and commits.
The repository has no security policy, leaving vulnerability reporting expectations unclear; the small, actively maintained project provides some compensation but does not remove the transparency gap.
The CI workflow lacks top-level token permissions, so its effective permissions are less explicit than recommended, although no write permissions were detected.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
guzzlehttp/guzzle Version ^7.13 || ^8.1 | — | — |
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.