The package is organized for ordinary PHP integration and has a clear consumer path. Its short history and one-person maintenance increase continuity risk, while the missing security policy leaves fewer documented safeguards.
68%
Total Score
75
100
88
83
The package is only 21 days old and has one release, so there is not yet enough history to establish durable maintenance. This is a maturity concern rather than evidence of abandonment.
One contributor made all 8 commits in the last 3 months, giving the project a bus factor of one. This makes fixes and future maintenance dependent on a single person.
Composer build tooling is present, but no security scanning tool was detected. The missing scanning automation is a modest hygiene gap, not a severe dependency risk by itself.
The repository has no security policy, leaving vulnerability-reporting and response expectations undocumented. This lowers transparency for a client that handles API credentials and shipment data.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
guzzlehttp/guzzle Version ^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.