codeages/omnipay-alipay
It has a clear MIT license, tests, a changelog, and a matching organization-owned repository. The absence of a security policy and automated scanning adds exposure, while the old release should be pinned deliberately.
57%
Total Score
75
88
50
Health Score Breakdown
The package has 50 releases and a historical median interval of about 19 days, but it has had no release in roughly 6 years. That long release gap is a meaningful maintenance concern.
The repository recorded no commits and no active maintainers in the last 3 months. Combined with the lack of recent registry releases, this points to substantially reduced maintenance activity.
Composer is used as the build tool, but no security scanning tools are configured. The missing scanning is a hygiene gap for a payment integration package.
The repository has no security policy. For a package handling payment integrations, this weakens the documented process for reporting and handling vulnerabilities.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 Loki Else |
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 omnipay/common Version ^3.0 | — | — |
php-http/guzzle6-adapter Version * | — | — |
Weekly Downloads
Info
- Last Published
- 6 years ago
- Created
- 13 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.