It has a clear MIT license, a focused README, and a small dependency set. There is no security policy or scanning, leaving little evidence of ongoing support.
43%
Total Score
25
100
72
83
The package has had no release in about four years, with zero releases in the last 12 months. That prolonged gap materially raises abandonment risk for a payment integration.
There were zero commits and zero active maintainers in the last three months, consistent with maintenance having stopped after October 2022. This is the strongest evidence of abandonment risk.
The package and repository are owned by the same individual account, providing clear ownership but no organizational backing to offset the inactive maintenance record.
The repository has zero stars and forks and only one watcher, providing little external validation. For a small focused integration this is supporting caution rather than a verdict by itself.
The repository uses Composer, but no security-scanning tools were detected. The missing scanning is a modest transparency and maintenance concern.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
omnipay/common 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.