phoenixg/omnipay-pingpp
Its MIT license, small dependency set, readable documentation, and extensive packaged tests make the release easy to inspect. The source repository is archived, registry releases stopped nearly nine years ago, and recent commit activity is absent, leaving maintenance and compatibility risks.
18%
Total Score
0
100
58
50
Health Score Breakdown
The package has only two releases, with the latest published in September 2017 and none in the last 12 months. This long release gap materially raises abandonment and compatibility risk.
The repository recorded zero commits and zero active maintainers in the last three months. Combined with the archived state and old release history, this indicates no current maintenance capacity.
The linked repository is archived, a severe abandonment signal even though it was pushed in November 2023. Archived projects are unlikely to receive fixes or compatibility updates.
No build tool or security scanning tool was detected in the repository. That weakens ongoing quality and security oversight, though it is less decisive than the lack of maintenance.
The repository has no security policy. This is a transparency and maintenance gap, especially for a payment integration, although it is secondary to the stronger abandonment signals.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 Huang Feng |
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 omnipay/common Version ~2.0 | — | — |
Weekly Downloads
Info
- Last Published
- 9 years ago
- Created
- 9 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.