hjiash/easypay
The source still matches the package, uses a small runtime dependency set, and has no install-time scripts. It lacks a security policy or scanning, leaving a payment integration with limited current safeguards.
30%
Total Score
0
71
83
Health Score Breakdown
The package has only two releases, both from 2016, with no release in roughly 10 years. This is strong evidence of abandonment for a payment integration.
The repository recorded no commits and no active maintainers in the past three months, consistent with the last push occurring in 2016. This materially increases maintenance risk.
Composer build tooling is present, but no security scanning tools were detected. This is a hygiene gap, though it is less significant than the inactivity evidence.
The repository is not archived, which is a modest positive, but its last push was in 2016 and does not offset the long inactivity period.
The repository has no security policy. That leaves vulnerability reporting and response expectations unclear for payment-related code.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 hjiash |
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 omnipay/common Version ~2.0 | — | — |
guzzlehttp/guzzle Version ~6.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.