Clear documentation, tests, and release notes make integration easier. The stale release and inactive recent repository activity, together with conflicting license records, warrant checking maintenance plans and licensing before adoption.
58%
Total Score
50
100
79
75
The artifact contains license files, but the manifest declares GPL-3.0 while the detected license is MIT. This concrete mismatch creates legal ambiguity even though licensing is present.
The package has had no registry releases in the last 12 months, and its latest release was about 20 months ago. Its five releases over roughly three and a half years show an established but currently inactive cadence.
There were no commits and no active maintainers in the last three months. Combined with the stale release history, this points to currently inactive maintenance.
Composer build tooling is present, but no security scanning tools were detected. That is a hygiene gap, not evidence that the release is unsafe by itself.
The repository has no security policy. For a payment SDK, this reduces transparency around vulnerability reporting and maintenance response.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
guzzlehttp/psr7 Version ^2.4 | — | — |
guzzlehttp/guzzle Version ^7.5 | — | — |
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.