The README, tests, stable versioning, and organization-owned repository make the package easier to assess and maintain. Its lack of commits for more than four years and missing security policy leave meaningful uncertainty for a payments dependency.
55%
Total Score
75
88
50
The package has 209 releases, but none in the last 12 months and its latest release was published in May 2022. This strong historical record is outweighed by the prolonged release gap.
There were no commits and no active maintainers in the last three months, consistent with the repository's last push being more than four years ago. This materially raises abandonment risk for a payment integration.
Composer build tooling is present, but no security scanning tool is reported. For a payments package this is a modest transparency and maintenance weakness, not proof of unsafe code.
The repository has no security policy. That reduces transparency for reporting and handling issues in a package that processes payments.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
omnipay/paypal Version * | — | — |
solunes/master Version * | — | — |
omnipay/braintree Version * | — | — |
bileto/omnipay-payu Version ^0.6.0 | — | — |
ignited/laravel-omnipay Version 2.3 | — | — |
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.