The project is only about two months old, and its security process is still lightweight. Good documentation, repository tests, active recent commits, and a clear license provide useful support, but the workflow needs tighter dependency pinning.
60%
Total Score
75
100
88
67
The package is about two months old with 10 releases concentrated over roughly three days, showing active initial development but limited evidence of long-term maintenance.
All 22 recent commits came from one contributor, leaving maintenance highly concentrated and creating a meaningful continuity risk.
Composer build tooling is present, but no security-scanning tooling was detected, leaving automated supply-chain checks limited.
The repository has no security policy, which reduces transparency for reporting and handling vulnerabilities in a package intended for application development.
The sole workflow was fully analyzed with no injection or high-severity findings, but all 6 action references are unpinned, so workflow dependencies can change unexpectedly.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
illuminate/http Version ^11.0|^12.0|^13.0 | — | — |
illuminate/console Version ^11.0|^12.0|^13.0 | — | — |
illuminate/support Version ^11.0|^12.0|^13.0 | — | — |
illuminate/database Version ^11.0|^12.0|^13.0 | — | — |
illuminate/contracts Version ^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.