The package has a clear license, extensive tests, a changelog, and recent activity from two contributors. Its small audience, concentrated contributions, and lack of a security policy leave some maintenance and transparency risk.
82%
Total Score
67
100
94
83
The registry namespace and repository are owned by the same individual user, so the package has direct ownership alignment but not organization-level maintenance backing.
Two contributors were active in the last three months, but the leading contributor made 75% of commits. The second contributor provides some continuity, while ownership remains concentrated.
Composer build tooling is present, but no security scanning tools were detected. The missing scanning coverage is a modest transparency and maintenance gap rather than evidence of an unsafe release.
The repository has no published security policy, leaving vulnerability reporting and response expectations unclear for a payment-related Laravel integration.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
illuminate/http Version ^10.0|^11.0|^12.0|^13.0 | — | — |
illuminate/routing Version ^10.0|^11.0|^12.0|^13.0 | — | — |
illuminate/support Version ^10.0|^11.0|^12.0|^13.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.