Documentation, automated tests, licensing, and release notes are all present. The project is young, recent commit activity is absent, and all six workflow actions are unpinned; the registry also reports an inconsistent latest version.
65%
Total Score
50
100
81
75
Six releases in roughly 196 days, with a median interval of about 4 days, shows active early development. However, the short history means long-term maintenance is not yet established.
There were zero commits and zero active maintainers in the last three months. For a young integration package, that is a meaningful maintenance concern even though the repository was pushed recently.
Composer build tooling is present, but no security scanning tools were detected. The missing scanning is a modest supply-chain hygiene gap, not evidence of unsafe behavior by itself.
The repository has no security policy. For a payment-gateway integration handling authentication and webhooks, this reduces transparency about vulnerability reporting and response.
The assessed release is 1.1.0, while the registry reports 0.2.0 as the latest version and no stable major version. This inconsistency weakens release maturity and makes the published version state harder to interpret.
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/support Version ^10.0|^11.0|^12.0|^13.0 | — | — |
illuminate/contracts 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.