Clear licensing, tests, and organization ownership improve transparency. No security policy or scanning leaves safeguards unclear.
45%
Total Score
50
100
70
75
This is the only release, published on June 24, 2021, with no releases in roughly five years. That strongly suggests abandonment risk for a payment integration.
The repository recorded zero commits and zero active maintainers in the last three months, consistent with the long release gap and limited evidence of ongoing maintenance.
Composer build tooling is present, but no security scanning tools were detected. That weakens automated safeguards even though the package has a defined build system.
No security policy is present, so there is no documented process for reporting or handling vulnerabilities. This matters for a package involved in payment processing.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
omnipay/common Version ^3 | — | — |
php-http/guzzle6-adapter 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.