Clear documentation, tests, and licensing support adoption, while missing security scanning and unpinned CI actions add maintenance risk. The repository is not archived and matches the package, but ongoing support looks limited.
55%
Total Score
50
81
75
The latest release was in February 2021, with no releases in the last 12 months. This is a substantial maintenance concern for a payment API adapter, despite the package having seven releases overall.
The repository recorded zero commits and zero active maintainers in the last three months, indicating limited recent development. Its last push in November 2024 provides some evidence of later activity but does not offset the current slowdown.
There were no new or closed issues or pull requests in the last month, while two issues and two pull requests remain open. This suggests limited visible maintenance, though the small project size makes the signal less severe.
Composer build tooling is present, but no security scanning tools were detected. For a package handling payment integrations, that is a meaningful transparency and maintenance gap.
The single workflow was fully analyzed with no dangerous triggers or audit findings, but all six action references are unpinned. This leaves CI dependent on mutable action versions and is a moderate supply-chain hygiene concern.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
guzzlehttp/guzzle Version ^6.5|^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.