Clear documentation, tests, and a lightweight dependency footprint reduce integration friction. Recent releases are encouraging, but payment-related maintenance rests with one active contributor and lacks dedicated security processes.
68%
Total Score
50
100
94
83
The repository owner is an individual rather than an organization, so there is no provided evidence of organizational handoff capacity to offset the concentrated contributor activity.
One contributor made 100% of the four recent commits. That concentration creates a meaningful continuity risk for a payment library, with no second active contributor shown.
Four commits were made in the last three months, showing recent activity, but all activity came from one maintainer, limiting evidence of resilient maintenance capacity.
Composer build tooling is present, but no security-scanning tools were detected. For a payment gateway library, that is a genuine security-maintenance gap rather than a cosmetic omission.
The repository has no security policy. This weakens vulnerability-reporting and response transparency 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.