meebio/omnipay-secure-trading
The code is easy to inspect, clearly identified, licensed, and backed by repository tests and release notes. However, no commits or releases have appeared for roughly six years, and the project has no security policy or scanning tools.
55%
Total Score
75
88
50
Health Score Breakdown
The package has only three releases and none in the last 12 months; its latest registry release was about seven years ago, indicating weak ongoing maintenance.
The repository recorded zero commits and zero 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, leaving a meaningful security-maintenance gap for this type of package.
The repository has no security policy, leaving vulnerability-reporting expectations unclear for a payment-processing integration.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 John Jablonski |
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 omnipay/common Version ~2.0 | — | — |
Weekly Downloads
Info
- Last Published
- 7 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.