Licensing, documentation, and repository ownership are clear. The long pause makes future compatibility and fixes uncertain, especially for a payment integration.
43%
Total Score
75
67
75
The latest release was about 6 years ago, with no releases in the last 12 months. Four releases arrived within roughly 14 days in 2020, but there is no evidence of subsequent maintenance.
There are no open issues or pull requests and no recent activity. While this avoids an unresolved backlog, it also provides no evidence of active project support.
The repository has 0 stars and 0 forks, with only 1 watcher. Popularity is not decisive, but these values provide little supporting evidence of broad community use or review.
The repository is not archived, which preserves a path for maintenance, but its last push was about 6 years ago and does not offset the stale release history.
The linked repository has no security policy. This is a transparency and maintenance gap for a payment-related integration, although it is not evidence of malicious behavior.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
craftcms/cms Version ^3.1.5 | — | — |
craftcms/commerce Version ^2.0|^3.0 | — | — |
batchnz/omnipay-flo2cash Version ^1.1.1 | — | — |
craftcms/commerce-omnipay Version ^2.0.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.