Usable with caveats: it is licensed, documented, tested, and not deprecated or archived, but the release has had no new registry version for over five years and the repository shows no recent commit activity. Depend on it only if its older payment integrations remain compatible with your needs.
58%
Total Score
50
100
83
83
The repository recorded zero commits and zero active maintainers during the last three months. Combined with the old registry release, this is the strongest abandonment concern in the available evidence.
The package has 31 releases since 2013, but its latest release was over five years ago and it had no releases in the last 12 months. That is a meaningful maintenance and compatibility concern for a payment integration.
There is one open issue and two open pull requests, with no new or closed issues or merged pull requests in the last month. This suggests limited current project activity.
The repository has no stars, three forks, and one watcher, indicating a very small public footprint. Popularity is supporting evidence rather than decisive, but this offers little external maintenance signal.
The repository uses Composer for builds, but no security scanning tools were detected. The missing scanning is a transparency gap, though the build tooling and tests provide some compensating evidence.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
omnipay/common Version ^3.1 | — | — |
php-http/discovery Version ^1.14 | — | — |
php-http/guzzle7-adapter Version ^1 | — | — |
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.