Risky to adopt: the package has had no release or repository commit activity for about seven years, which creates substantial abandonment risk for a payment integration. It remains licensed, documented, tested, and not deprecated or archived, but those strengths do not offset the lack of current maintenance.
45%
Total Score
0
100
75
75
The latest release was published about seven years ago, and there were no releases in the last 12 months. The six-release history shows an initially established project, but no recent maintenance for this payment integration is a significant concern.
The repository recorded zero commits and zero active maintainers in the last three months, consistent with the package's long release gap. This is strong evidence of abandonment risk rather than merely a cosmetic documentation gap.
The repository has zero stars, forks, and watchers, offering no supporting community evidence. Low popularity alone is not decisive, but alongside seven years of inactivity it provides no compensating maintenance signal.
No security policy was found in the repository. This weakens vulnerability-reporting transparency, although the absence of repository workflows limits the practical significance of this gap.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
omnipay/common Version v3.0.2 | — | — |
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.