Risky to adopt for a new payment integration: the release is over five years old and the repository shows no recent maintenance. It has a clear MIT license, tests, documentation, and a small dependency surface, but the linked repository does not identify the package in its name or README.
42%
Total Score
0
100
71
83
The latest release was published on December 31, 2020, with no releases in the last 12 months. That long period without a release materially raises abandonment and compatibility risk.
The repository recorded zero commits and zero active maintainers during the last three months, consistent with the package having received no meaningful maintenance for over five years.
The repository name does not match the package name and its README does not mention the package, so the source relationship is less transparent even though the repository URL is linked directly.
The repository has only 1 star, 0 forks, and 1 watcher. Popularity is not decisive for a small payment driver, but it provides little evidence of broad review or community support.
No security policy was found. This is a transparency gap for a payment-processing integration, although the absence of a policy alone does not establish an active security problem.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
omnipay/common 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.