smodav/ipay
It has a clear README, matching source repository, MIT licensing, and a small dependency footprint. Missing a security policy and security scanning reduce transparency, but do not offset the maintenance gap.
38%
Total Score
25
100
81
83
Health Score Breakdown
The package has had only two releases, both in June 2017, with no releases in the last 12 months after roughly nine years of age. This is strong evidence of abandonment for a payment-integration library.
There were no commits and no active maintainers in the last three months, consistent with the release history and indicating that defects or compatibility changes may go unaddressed.
The repository is owned by an individual user rather than an organization, so there is no visible organizational backing to compensate for the single-maintainer publishing setup or prolonged inactivity.
Composer is used for the build, but no security-scanning tools are present. This is a transparency and hygiene gap, though it is less significant than the prolonged inactivity.
The repository has no security policy, leaving no documented path for reporting vulnerabilities or explaining security handling. This lowers transparency for a package processing payments.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 SmoDav |
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 guzzlehttp/guzzle Version ^6.2 | — | — |
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.