Usable with caveats: it has a long release history, a current stable release, and organization-backed maintenance. The linked repository has only one recent contributor and does not identify this package in its README, so verify the source relationship before adopting it broadly.
68%
Total Score
67
100
86
50
All one recent commit came from a single contributor, leaving maintenance dependent on one active individual. Organization backing provides some handoff capacity, but no second active contributor is evidenced.
The repository recorded one commit in the last three months from one active maintainer, showing recent activity but a very thin current maintenance rate.
The repository name does not match the package name and its README does not mention this package, so the package-to-source relationship is not transparent. The Magento-oriented repository may be a related monorepo or adapter source, but that connection is not demonstrated by this signal.
The repository uses Composer for builds, supporting reproducible package work, but no security scanning tools were detected. This is a transparency and maintenance gap rather than evidence of unsafe code.
The repository has no security policy, leaving vulnerability reporting and response expectations undocumented for an integration package that handles payment APIs.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
guzzlehttp/guzzle Version >=6.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.