yasinkuyu/omnipay-gvp
The MIT license, clear README, and included tests make the package understandable to adopt. It lacks security scanning and a security policy, so payment integrations should be treated as higher-maintenance work for the adopter.
42%
Total Score
0
100
81
50
Health Score Breakdown
Only two releases were published, both in August 2015, with no releases in the last 12 months; this strongly indicates abandonment risk for a payment gateway.
The repository has had zero commits and zero active maintainers in the last three months, while its last push was about 9 years ago; there is no evidence of ongoing maintenance.
Composer build tooling is present, but no security scanning tools were detected; this is a transparency and maintenance gap for a package handling payment integrations.
The repository has no security policy, leaving no documented channel or process for reporting vulnerabilities; this adds a modest transparency concern.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 Yasin Kuyu |
| Omnipay Contributors |
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 omnipay/common Version ~2.0 | — | — |
Weekly Downloads
Info
- Last Published
- 11 years ago
- Created
- 11 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.