The MIT license and matching repository make its provenance clear. Its single runtime dependency keeps the integration small, but the codebase lacks tests and security documentation.
43%
Total Score
33
100
67
50
The latest release was about seven years ago, with no releases in the last 12 months and only two releases overall. This strongly indicates abandonment risk despite the package not being deprecated.
The repository recorded zero commits and zero active maintainers in the last three months, consistent with the roughly seven-year release gap. No current maintenance capacity is visible.
Only one registry maintainer is listed. A single maintainer is not inherently unhealthy for a small package, but it leaves little visible redundancy alongside the long period without updates.
The package and repository are owned by the same individual account. This supports provenance, but it does not provide the capacity or redundancy of organization backing.
Composer build tooling is present, but no security scanning tools are configured. This is a maintenance and transparency gap for a payment-processing integration.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
league/omnipay Version ^3 | — | — |
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.