neerajsohal/omnipay-paytm
The package has a focused dependency profile, a README, tests, and matching MIT licensing. Its last release and repository push were about nine years ago, with no recent commits or security policy, leaving substantial abandonment risk.
36%
Total Score
0
100
67
50
Health Score Breakdown
The package has four releases, but none in the last 12 months and the latest release was about nine years ago. This strongly indicates that maintenance has stopped.
The repository recorded no commits and no active maintainers in the last three months, consistent with the long release gap and increasing abandonment risk.
Composer build tooling is present, but no security-scanning tools were detected. This is a modest transparency and maintenance gap, though it is less significant than the prolonged inactivity.
The repository is not archived, which avoids an explicit abandonment marker, but its last push was about nine years ago and does not offset the inactive commit history.
The repository has no security policy. For a payment-processing integration, this weakens the project's transparency and gives maintainers no documented channel for reporting security issues.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 Neeraj Kumar |
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 omnipay/common Version ^2.5 | — | — |
Weekly Downloads
Info
- Last Published
- 9 years ago
- Created
- 11 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.