The package includes a README, tests, and a small dependency set, but has no security policy and little adoption evidence. Its ownership is transparent, though ongoing support capacity is unclear.
42%
Total Score
25
100
75
83
The latest registry release was published over eight years ago, with no releases in the last 12 months. This is strong evidence of abandonment risk for a payment integration.
The repository recorded no commits and no active maintainers in the last three months, consistent with the long release gap and indicating no current maintenance activity.
There were two open issues but no issues or pull requests were created, closed, or merged in the last month. This suggests little recent project engagement.
The repository uses Composer build tooling, but no security scanning tools were detected. This is a modest transparency and maintenance gap rather than a severe issue.
No security policy was found in the repository, leaving the process for reporting payment-related vulnerabilities unclear.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
omnipay/common Version ^3.0 | — | — |
php-http/guzzle6-adapter Version ^1.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.