Usable with caveats: the package is clearly licensed, tested, documented, and actively maintained, but it is very new and all recent commits come from one contributor. The repository also lacks a security policy and explicit workflow token permissions.
72%
Total Score
50
100
88
67
The package and repository are owned by the same individual account, which supports ownership consistency but does not provide the resilience of organization-backed maintenance.
The package is only 39 days old with two releases, so its maintenance record is limited; however, the latest release is recent rather than stale.
One contributor made all six recent commits, creating a meaningful continuity risk if that maintainer becomes unavailable; the repository is user-owned, so no organizational handoff is evident.
Six commits were made in the last three months, showing recent activity, but all activity came from one active maintainer.
Composer build tooling is used, but no security-scanning tool was detected. This is a transparency and maintenance gap rather than evidence that the package is unsafe.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
guzzlehttp/guzzle Version ^7.0 | ^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.