The MIT license, clear README, and substantial test suite make the package straightforward to inspect and integrate. Its lack of security scanning and very small repository footprint leave less assurance for a payment integration.
55%
Total Score
25
100
81
75
The package has 13 releases, but none in roughly seven years; the latest registry release was published in June 2019. That long silence is a substantial maintenance concern for a payment integration.
There were zero commits and zero active maintainers in the last three months, consistent with the long release gap and indicating no observed ongoing maintenance.
The repository is owned by an individual account rather than an organization, so the small maintainer base offers limited visible organizational backing.
Composer build tooling is present, but no security scanning tools were detected. This is a modest transparency and maintenance gap rather than evidence that the package is unsafe.
The repository has no security policy, leaving vulnerability reporting expectations undocumented. This is a meaningful but limited concern because other source and test documentation is present.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
omnipay/common Version ^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.