omnipay/bitpay
MIT licensing, tests, and release notes improve transparency. The repository has no security policy or security scanning, so future fixes may be harder to assess.
38%
Total Score
33
100
69
88
Health Score Breakdown
The package has had only one release, first published over 10 years ago, with no releases in the last 12 months. This strongly indicates abandonment risk.
There were no commits or active maintainers in the last three months, consistent with the package's long release gap and increasing abandonment risk.
The repository is owned by an organization, which provides some project context, but the observed release and commit inactivity outweighs that administrative backing.
There has been no recent issue or pull request activity. Combined with the lack of commits, this provides no evidence of current maintenance.
Composer is used for builds, but no security scanning tool is present. The missing scanner is a modest transparency and maintenance concern, not a standalone adoption blocker.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 Adrian Macneil |
| Omnipay Contributors |
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 omnipay/common Version ~2.0 | — | — |
Weekly Downloads
Info
- Last Published
- 10 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.