The single maintainer and missing security policy reduce independent oversight for a payment integration. Clear documentation, tests, licensing, and a matching repository provide useful adoption and maintenance evidence.
79%
Total Score
75
100
94
75
Only one registry maintainer is listed. That is plausible for a user-owned project, but it leaves limited visible publishing redundancy if that person becomes unavailable.
Composer build tooling is present, but no security-scanning tooling is reported, leaving less automated protection against dependency or code issues.
The repository has no security policy, leaving vulnerability-reporting expectations and response procedures unclear for a package that handles payments.
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 | — | — |
illuminate/validation 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.