sroor/laravel-payment
MIT licensing and clear usage instructions make adoption easier, and the repository is not archived. The single-maintainer project has no recent commits or releases and lacks a security policy, increasing maintenance uncertainty.
38%
Total Score
25
75
50
Health Score Breakdown
The package has made no releases in the last 12 months, and its last release was in June 2023 despite being about three years old. This is strong evidence of abandonment risk for a payment integration.
There were zero commits and zero active maintainers during the last three months, consistent with the long release gap and materially raising abandonment risk.
Only one registry maintainer is listed, leaving little visible publishing redundancy for a package that handles payment integration.
A readable README and GitHub release are present. The absence of published tests and a changelog is normal for package artifacts, while the repository also reports no tests, limiting confidence in changes.
Composer build tooling is present, but no security-scanning tools were detected. This is a transparency and maintenance gap for a package handling payment credentials and webhooks.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 Kamal Sroor |
Direct Dependencies
No direct dependencies.
Weekly Downloads
Info
- Last Published
- 3 years ago
- Created
- 3 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.