The package includes a clear README, changelog, MIT license, and no install-time scripts. Its small repository has no security scanning or security policy, leaving future maintenance and response capacity uncertain.
58%
Total Score
50
80
75
This is the package's only release, published nearly two years ago, with no releases in the last 12 months. That leaves little evidence of ongoing maintenance.
The repository recorded zero commits and zero active maintainers in the last three months. With only one release, this provides no recent evidence that fixes or updates are being made.
Composer build tooling is present, but no security scanning tools were detected. That is a maintenance and transparency gap for a payment integration library.
The repository has no security policy. For code handling payment requests and signature validation, the absence of a documented reporting path modestly lowers confidence in ongoing maintenance.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
omnipay/common Version ^3.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.