Clear documentation, tests, and licensing make integration easier. Organization ownership and the matching repository provide useful provenance, while the lack of a security policy leaves a modest transparency gap.
65%
Total Score
83
100
89
83
The package is only 2 days old with 2 releases, so there is not enough release history to establish long-term maintenance reliability.
There were no commits or active maintainers in the last 3 months, but the repository and package are only 2 days old, so this is limited evidence rather than proof of abandonment.
Composer build tooling is present, but no security scanning tool was detected, leaving a modest repository hygiene gap.
The repository has no security policy, which reduces transparency for reporting and handling vulnerabilities in a payment integration package.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
illuminate/http Version ^10.0|^11.0|^12.0 | — | — |
guzzlehttp/guzzle Version ^7.5 | — | — |
illuminate/routing Version ^10.0|^11.0|^12.0 | — | — |
illuminate/support Version ^10.0|^11.0|^12.0 | — | — |
illuminate/contracts 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.