Usable with caveats: it is a long-established, stable package with frequent releases, clear licensing, and organization backing. Recent repository activity is absent, and its workflow lacks explicit token permissions while using pull-request-triggered automation.
72%
Total Score
83
100
93
50
One workflow uses pull_request_target, which can expose privileged automation to pull-request events; no untrusted checkout or script injection was detected, limiting the concern.
The repository recorded 0 commits and 0 active maintainers in the last 3 months. The recent push and ongoing release history partly offset this, but the current development activity is still a meaningful maintenance concern.
Composer build tooling is present, but no security scanning tools were detected. This is a transparency and assurance gap, though it is not by itself evidence that the package is unsafe.
The sole workflow has no top-level token permissions declaration. It does not request explicit top-level write access, but the missing restriction leaves permissions less transparent than they should be.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
illuminate/support Version ^13.0 | — | — |
illuminate/contracts Version ^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.