The MIT license, README, and repository tests make the package transparent to integrate. Security scanning is absent, and the small maintainer base may limit future fixes.
42%
Total Score
0
100
79
67
The latest release was published on June 19, 2019, with no releases in the last 12 months. This long period without updates is a major abandonment concern for a payment integration.
The repository recorded zero commits and zero active maintainers over the last three months, consistent with the package having been inactive since June 2019.
Composer build tooling is present, but no security scanning tools were detected. That weakens ongoing maintenance hygiene, especially for a payment-related package.
The repository has no security policy. This is a transparency and vulnerability-reporting gap, although it is less important than the prolonged inactivity.
No GitHub Actions workflows were present, so there are no workflow risks to score. This also means there is no workflow-based evidence of current automated maintenance.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
omnipay/common Version ^3.0 | — | — |
php-http/guzzle6-adapter Version * | — | — |
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.