Epay payment gateway class for Laravel
58%
Total Score
50
78
90
The registry lists one maintainer, creating a narrow publishing and continuity base; the repository owner is a user account rather than an organization, so there is no provided organizational backing to offset that limitation.
A substantive README is present, but neither the artifact nor repository contains tests or a changelog; for a payment integration, the absence of repository tests is a meaningful maintenance and regression concern.
The repository owner is a user account, not an organization, so the available evidence does not show institutional backing that would reduce single-owner continuity risk.
Only three releases have been published over 589 days, with one release in the last 12 months and a median interval of about 295 days; this indicates limited release and maintenance momentum.
There were zero commits and zero active maintainers in the last three months, indicating a current maintenance gap that is only partly offset by the repository's recent push timestamp.
We didn't find any vulnerabilities for this package.
No direct dependencies.
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 27001Compliant
ISO 42001Compliant© All Intel data is openly available and commercially licensed.