Tests, licensing, and a focused repository support adoption. The missing security policy and scanning leave less transparency for a payment integration; pin 1.5.0 and verify provider compatibility.
58%
Total Score
67
100
88
75
The latest release was over four years ago, with no releases in the last 12 months. Fifteen releases over the package's lifetime show prior activity but do not offset the current pause.
There were no commits and no active maintainers in the last three months. Combined with the old latest release, this indicates a meaningful risk of stalled maintenance.
There were no new or closed issues or pull requests in the last month, while two pull requests remain open. This provides little evidence of current maintenance.
Composer build tooling is present, but no security scanning tools were detected. For a payment integration, the missing automated security coverage is a transparency and maintenance gap.
The repository has no security policy. That leaves vulnerability reporting and response expectations unclear for a package handling payment integrations.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
league/omnipay Version ^3.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.