Tests, documentation, and matching MIT licensing provide a solid baseline. The project has had no release or commit activity for over five years, while its payment-focused code lacks a security policy and automated security scanning.
42%
Total Score
0
75
50
The latest release was published in March 2021, with no releases in the last 12 months. For a payment gateway, this long pause is a substantial maintenance and compatibility concern.
The repository recorded zero commits and zero active maintainers in the last three months, consistent with the absence of recent releases. The repository is not archived, but there is no observed current development.
Composer build tooling is present, but no security scanning tools were detected. That is a meaningful hygiene gap for a package handling payment integrations.
The repository has no security policy, leaving no documented process for reporting or handling vulnerabilities in payment-processing code.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
jms/serializer Version ~1.7 | — | — |
omnipay/common Version ~2.0 | — | — |
paragonie/random_compat Version ~2.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.