The repository is very small, with no tests and no security policy, limiting confidence in changes and maintenance. Its MIT license and matching source repository provide useful transparency.
35%
Total Score
0
71
50
The latest of only three releases was published in December 2016, with no releases in the last 12 months. This is strong evidence of abandonment for a payment integration.
The repository recorded zero commits and zero active maintainers in the last three months, consistent with the package's long release gap and leaving little evidence of ongoing maintenance.
The artifact includes a README and this version has a GitHub release, but it has no tests or changelog and the repository also reports no tests or changelog. The missing tests materially reduce confidence in a payment package.
Composer is used as the build tool, but no security scanning tools are present. This is a modest supply-chain hygiene gap, not evidence that the release is malicious.
The linked repository has no security policy. This is a transparency and maintenance gap for a package handling payment credentials and transaction callbacks.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
omnipay/common Version ^2.5 | — | — |
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.