The workflows leave all six actions unpinned, and the repository has no security policy or scanning. A clear README, repository tests, regular releases, and no install-time scripts provide useful safeguards.
71%
Total Score
67
100
94
75
The repository is owned by a user account rather than an organization, so the single-contributor concentration is not visibly offset by organizational backing.
All three recent commits came from one contributor, leaving maintenance dependent on a single active person despite the broader release history.
Composer build tooling is present, but no security scanning tools were detected, leaving security hygiene less visible.
The repository has no security policy, so users have no documented process for reporting or handling vulnerabilities.
Both workflows were analyzed successfully with no dangerous triggers, untrusted checkouts, or audit findings, but all six action references are unpinned, reducing build reproducibility and update integrity.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
illuminate/cache Version ^6.0|^7.0|^8.0|^9.0 | — | — |
illuminate/config Version ^6.0|^7.0|^8.0|^9.0 | — | — |
illuminate/console Version ^6.0|^7.0|^8.0|^9.0 | — | — |
illuminate/support Version ^6.0|^7.0|^8.0|^9.0 | — | — |
illuminate/contracts Version ^6.0|^7.0|^8.0|^9.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.