The package has clear documentation, tests, a changelog, and an MIT declaration. Its repository is linked correctly, not archived, and has no install-time scripts, but the long gap since release leaves future compatibility uncertain.
60%
Total Score
50
88
75
The registry lists one maintainer account. That is a thin publishing base, and the absence of recent commit activity provides no observed evidence of a broader active maintenance team.
Only three releases exist, with none in the last 12 months; the latest release was about 15 months ago. This indicates a slow and currently inactive release cadence.
There were no commits and no active maintainers in the last three months, consistent with the repository's last push occurring around 15 months ago. This is a meaningful maintenance and abandonment concern.
Composer build tooling is present, but no security scanning tools were detected. This is a modest transparency and maintenance gap, not evidence that the package is unsafe.
The repository has no security policy. For an SDK that handles payment-service integration, this weakens the documented process for reporting and handling security issues.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
guzzlehttp/guzzle Version ^7.4 | — | — |
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.