Tests, a README, matching MIT licensing, and a small dependency surface support integration. The lack of repository security scanning leaves extra maintenance risk for payment-related code.
45%
Total Score
0
100
78
75
The package has had no release in about five years: its latest release was June 30, 2021, with zero 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 long release gap. The repository is not archived, but it shows no recent maintenance capacity.
The repository has zero stars and forks and only one watcher. Popularity is supporting evidence rather than a verdict, but this provides little evidence of a broad user or contributor base.
Composer build tooling is present, but no security-scanning tools are reported. That leaves payment-related changes without visible automated security coverage.
The linked repository has no security policy. This is a transparency and maintenance gap, especially for a package handling payment flows, and no other provided signal compensates for it.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
omnipay/common Version ~2.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.