futskito/redsys-omnipay
The README and small dependency set make integration straightforward. The project has had no releases or commits for more than four years, and its repository does not clearly identify this package, weakening confidence in ongoing support.
43%
Total Score
0
100
71
75
Health Score Breakdown
The package has 5 releases, but none in the last 12 months; its latest release was more than four years ago. This is strong evidence of abandonment risk.
The repository recorded no commits and no active maintainers in the last three months, consistent with its last push being more than four years ago. This materially increases maintenance and abandonment risk.
The repository name is sermepa-omnipay rather than futskito/redsys-omnipay, and its README does not mention the package name. The historical RedSys/Sermepa naming may explain the difference, but package ownership is still less clear.
Composer build tooling is present, but no security scanning tools were detected. This is a modest transparency and maintenance gap rather than evidence that the package is unsafe.
The repository has no published security policy, leaving vulnerability-reporting expectations unclear for a payment gateway integration.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 Javier Sampedro |
| NitsNets Studio |
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 omnipay/common Version 3.* | — | — |
redsys/messages Version * | — | — |
Weekly Downloads
Info
- Last Published
- 4 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.