Payever Integration for OroCommerce
68%
Total Score
67
50
89
83
Eight runtime dependencies, including several payment SDKs and OroCommerce, create meaningful integration and update surface, but the profile is plausible for a payment gateway plugin rather than inherently excessive.
The package has existed for about 3 years and has six releases, but only one release arrived in the last 12 months and the median interval is about 308 days, indicating slow maintenance cadence.
All recent commit activity comes from one contributor, creating a real continuity risk; organization ownership provides some handoff capacity but no second active contributor is shown.
Only one commit was recorded in the last 3 months, with one active maintainer, showing limited recent development despite the recent release.
Composer is used for builds, but no security scanning tools were detected. For a payment integration, that missing automated security coverage is a transparency and maintenance concern.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
oro/commerce Version 5.1.*|6.0.*|6.1.* | — | — |
setasign/fpdf Version ^1.8 | — | — |
payever/core-sdk-php Version 2.2.0 | — | — |
payever/plugins-sdk-php Version 2.0.1 | — | — |
payever/payments-sdk-php Version 2.8.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.