A clear README, included tests, MIT licensing, and a small dependency set support straightforward integration. The repository is not archived, but it has no security policy, leaving maintenance and vulnerability reporting less transparent.
55%
Total Score
50
100
90
50
The package has had no release in over 10 years and none in the last 12 months, which is a substantial maintenance concern for a payment integration. Its stable release history provides some maturity but does not offset the long gap.
The repository recorded zero commits and zero active maintainers in the last three months, indicating little current development activity. A push in January 2023 shows it is not entirely abandoned, but activity remains stale.
No repository security policy was found, reducing transparency about vulnerability reporting and response. This is a hygiene gap rather than evidence that the package is unsafe.
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.