invoiceninja/omnipay-collection
Its 28 runtime dependencies widen upgrade and compatibility risk, while the repository has no security policy or automated security scanning. The matching repository and MIT licensing provide useful transparency, but not enough to offset the stale project.
38%
Total Score
50
50
79
83
Health Score Breakdown
The latest release was in November 2020, with no releases in the last 12 months; this is strong evidence that the package is no longer actively maintained.
The repository recorded zero commits and zero active maintainers in the last three months, consistent with the long release gap and elevated abandonment risk.
The package declares 28 runtime dependencies, including many payment drivers, creating substantial compatibility and update exposure for a package with no recent maintenance.
There were no new or closed issues or pull requests in the last month, while one issue and one pull request remain open; this suggests little ongoing project attention.
Composer build tooling is present, but no security scanning tools are configured, leaving a meaningful repository hygiene gap.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 Hillel Coren |
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 omnipay/bitpay Version dev-master | — | — |
omnipay/mollie Version 3.* | — | — |
omnipay/stripe Version ~2.0 | — | — |
omnipay/omnipay Version ~2.3 | — | — |
omnipay/payfast Version dev-master | — | — |
Weekly Downloads
Info
- Last Published
- 5 years ago
- Created
- 8 years ago
Are You Affected?
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 27001CompliantISO 42001Compliant
FedRAMPImplementing© All Intel data is openly available and commercially licensed.