dilab/omnipay-2c2p
The package has a clear README, focused dependencies, tests, and a matching source repository. Its small user base, absent security policy, and inactive recent development leave more maintenance risk than a current library.
56%
Total Score
38
100
78
88
Health Score Breakdown
Only two releases were published, with the latest in April 2018 and none in the last 12 months; that is over eight years without a release and materially raises abandonment risk.
There were zero commits and zero active maintainers in the last three months; combined with the old latest release, this points to inactive maintenance.
One registry maintainer is a thin publishing base for an individual-owned project, leaving limited visible redundancy if that maintainer stops supporting it.
The registry namespace and repository owner match, but the owner is an individual account rather than an organization, so there is no demonstrated organizational backing.
There is one open issue and no issue or pull-request activity in the last month, offering little evidence of active community maintenance.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 xu ding |
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 omnipay/common Version 3.0-beta.1 | — | — |
php-http/guzzle6-adapter Version ^1.1 | — | — |
Weekly Downloads
Info
- Last Published
- 8 years ago
- Created
- 10 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.