Healthy and usable for production, with some security-process caveats. It has regular releases, a current stable version, tests, release notes, and an organization-backed repository, but recent repository activity is quiet and the project lacks a security policy and explicit workflow permissions.
76%
Total Score
67
100
89
80
There were no commits and no active maintainers in the last three months, which is a maintenance warning. However, the recent release history and May 19 repository push show that the project is not clearly abandoned.
There are no open issues and one open pull request, but no issues or pull requests were closed in the last month. This provides little evidence of active issue handling.
The repository has only 3 stars, 3 forks, and no watchers. This is limited adoption evidence, but popularity is supporting context rather than a decisive health concern when release and ownership signals are positive.
Composer build tooling is present, but no security scanning tools were detected. This is a process gap, though it is not by itself evidence that the package is unsafe or unmaintained.
The repository has no security policy, leaving vulnerability-reporting and response expectations undocumented. The absence is a transparency gap for a payment-processing SDK.
We didn't find any vulnerabilities for this package.
No direct dependencies.
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.