omnipay/metacharge
It includes tests, a clear MIT license, and release notes for this version. The repository has no security policy, and publishing is controlled by one person.
40%
Total Score
50
80
75
Health Score Breakdown
Only one registry account has publishing access. Because the repository is user-owned rather than organization-backed, this leaves a relatively thin visible maintenance base and increases continuity risk.
The package has only two releases, with the latest published on October 28, 2014, and none in the last 12 months. This long period without releases is strong evidence of abandonment risk for a payment integration.
The repository is not archived, which preserves a basic path for maintenance, but it was last pushed on October 29, 2014. The lack of source updates for more than 11 years materially lowers confidence in ongoing support.
The linked repository has no security policy. For a payment-processing integration, this is a meaningful transparency gap, although it does not by itself show that the package is unsafe.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 Tom Sowerby |
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 omnipay/common Version ~2.0 | — | — |
Weekly Downloads
Info
- Last Published
- 11 years ago
- Created
- 12 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.