The MIT license, tests, changelog, and organization-backed repository provide useful maintenance safeguards. However, only two commits in the last three months, no security policy, and four unpinned workflow actions leave meaningful maturity and build-integrity concerns.
68%
Total Score
88
100
78
75
There were 17 releases in about one month, with a median interval of roughly 5 hours; this shows active publishing but also a very young and unusually fast-moving project.
Only two commits were recorded over the last three months. That is limited observed maintenance for an actively published SDK and lowers confidence in ongoing support.
The repository has no stars, forks, or watchers. This is weak supporting evidence for maturity, though popularity alone does not determine health.
Composer build tooling is present, but no security scanning tools were detected, leaving a modest supply-chain hygiene gap.
The repository has no security policy, which makes vulnerability-reporting and disclosure expectations less transparent for a payment SDK.
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.