Usable with caveats: the package is clearly backed by a matching organization repository and has a stable release with release notes, but maintenance evidence is thin. It has only two releases, no commits in the last three months, and no security policy or scanning, which matters for payment integration code.
60%
Total Score
75
100
83
50
Only two releases have been published since March 2025, with no releases in the last 12 months. This provides limited evidence of ongoing maintenance for a payment integration package.
The repository recorded zero commits and zero active maintainers in the last three months. Combined with the sparse release history, this is meaningful evidence of slow maintenance.
The repository has one star and no forks or watchers. This is weak supporting evidence and does not by itself indicate that the package is unsafe, but it offers little external validation.
The repository uses Composer, but no security-scanning tools are configured. For code handling payment credentials and webhooks, the lack of automated security checks is a maintenance and transparency concern.
The repository has no security policy. That leaves vulnerability reporting and response expectations unclear for a package handling payment flows.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
razorpay/razorpay Version ^2.8 | — | — |
illuminate/support Version ^10.0|^11.0|^12.0 | — | — |
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.