What a Laravel application needs to run on Brewless: the release, schedule and queue routes its own containers answer on, and trust in the edge in front of it.
68%
Total Score
caution
Only two same-day releases exist, while all four workflow actions are unpinned and no security policy is provided.
The package is only 0 days old and has just 2 releases, both published within the same day. That is too little history to demonstrate durable maintenance, though it is not evidence of abandonment by itself.
Composer build tooling is present, but no security-scanning tooling was detected. This is a modest hygiene gap, not a severe risk, especially given the clean workflow audit.
The repository has no security policy. For a package exposing operational HTTP routes, this is a transparency and vulnerability-reporting gap that is not covered by another provided signal.
Version v0.2.0 is not a prerelease, but it is below 1.0 and therefore signals an early-stage API and maturity level.
The single workflow was fully analyzed with no dangerous triggers, untrusted checkouts, script injection, or audit findings. However, all 4 of 4 action references are unpinned, leaving avoidable reproducibility and action-supply-chain risk.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
illuminate/http Version ^12.0 || ^13.0 | — | — |
illuminate/cache Version ^12.0 || ^13.0 | — | — |
illuminate/console Version ^12.0 || ^13.0 | — | — |
illuminate/routing Version ^12.0 || ^13.0 | — | — |
illuminate/support Version ^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.