This is a generally usable and transparently packaged release with a long history since 2019, 52 releases, 16 releases in the last 12 months, a stable non-prerelease version, an active non-archived organization-owned repository, repository tests, and no install-time lifecycle scripts. The main concern is maintenance evidence: the repository recorded no commits and no active maintainers in the last 3 months, despite the strong registry release cadence, and it lacks a security policy and automated security scanning. The low repository popularity is supporting context rather than a decisive problem. A developer can consider version 5.3.0, but should verify ongoing maintainer responsiveness before adopting it for a payment-critical integration.
72%
Total Score
88
100
89
88
No commits and no active maintainers were observed in the last 3 months, creating a genuine maintenance concern; the frequent registry releases partly compensate but do not replace recent source-activity evidence.
With 6 stars and 1 fork, the repository has limited external adoption signals. This is a modest caution about community validation, but popularity alone is not a health verdict for a small SDK.
Composer build tooling is present, but no security scanning tools are configured. The missing scanning is a hygiene gap for a payment integration, though it is not by itself evidence of unsafe code.
The repository has no security policy, leaving vulnerability reporting and disclosure expectations unspecified for a package handling payment integrations.
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.