fruitcakestudio/omnipay-rabobank
The MIT license, README, and repository tests make the package easier to evaluate and integrate. Its tiny project footprint and lack of a security policy add transparency concerns, despite no deprecation or archive status.
35%
Total Score
50
71
50
Health Score Breakdown
The package has had one release, published about 11 years ago, with no releases in the last 12 months. This is strong evidence of abandonment for a payment integration.
The repository recorded zero commits and zero active maintainers in the last three months, consistent with the release history and indicating no current maintenance capacity.
The repository has only 2 stars and 1 fork, providing little supporting evidence of community review or shared maintenance. Popularity is not decisive, but it does not compensate for the long inactivity.
The linked repository is not archived, so the project has not been formally marked discontinued. However, its last push was about 11 years ago, limiting the reassurance this provides.
The repository has no security policy, leaving no documented path for reporting payment-related vulnerabilities. This is a transparency gap, although it is secondary to the maintenance risk.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 Adrian Macneil |
| Omnipay Contributors |
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 omnipay/common Version ~2.0 | — | — |
Weekly Downloads
Info
- Last Published
- 12 years ago
- Created
- 12 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.