Will It Vibe?No timeout-minutes set
Part of Testing & CI, which counts for 10% of the overall score. When this check fires it deducts 4 points from that category, once per scan, no matter how many places it turns up.
What it detects
No job or step in the workflow sets timeout-minutes. A hung step (a stuck test, a network wait) then runs until the six-hour default, burning runner minutes and holding concurrency slots. This is a heuristic reliability flag.
Why it matters
With no timeout-minutes anywhere, a stuck step (a hung test, a wait on a service that never comes up, an interactive prompt) keeps the job running until the six-hour default limit. That burns runner minutes, holds a concurrency slot, and delays feedback. This is a heuristic reliability flag.
How to fix it
Set timeout-minutes on each job to a value comfortably above its normal runtime (for example 15 or 30). For steps that are prone to hanging, set a tighter step-level timeout-minutes as well so one bad step fails fast instead of stalling the whole job.
The paid report includes a ready-to-paste prompt for your AI coding agent for every check it finds, pointed at the exact findings from your scan. See pricing
Does your repo trip this check?
Paste a GitHub URL or drop a project folder. Scans run in your browser and take seconds.
Scan your repo