lsv/omnipay-epay
The MIT license, tests, and matching source repository provide useful transparency. Its small community and lack of security scanning offer little evidence of ongoing support.
38%
Total Score
0
75
50
Health Score Breakdown
The package has only one release, published about 12 years ago, with no releases in the past 12 months. That strongly raises abandonment risk for a payment integration.
The repository has had zero commits and zero active maintainers in the past 3 months, while its last push was about 9 years ago. This is strong evidence that maintenance has stopped.
The repository has only 3 stars and 3 forks, providing little community evidence to offset the lack of recent maintenance.
The project uses Composer and Phing, showing some build structure, but it has no security scanning tools. The tooling is adequate for organization but weak for ongoing security assurance.
The repository has no published security policy, leaving vulnerability reporting and response expectations unclear. This matters for a package handling payment integrations.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 Martin Aarhof |
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 omnipay/common Version 2.* | — | — |
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.