Will It Vibe?Legacy backtick command substitution
Part of Code Quality & Syntax, which counts for 20% of the overall score. When this check fires it deducts 2 points from that category, once per scan, no matter how many places it turns up.
What it detects
Backtick substitution (`cmd`) works identically to $(cmd) but nests awkwardly (each inner backtick must be escaped) and is harder to read at a glance. This is a pure style call with no functional difference; $(...) is the modern, universally recommended form.
Why it matters
Backtick command substitution (`cmd`) behaves identically to $(cmd) at runtime, but nesting it requires escaping every inner backtick, which gets unreadable fast, and most style guides and linters flag it as legacy. This is a pure readability/style issue, not a functional bug.
How to fix it
Replace `cmd` with $(cmd). They are drop-in equivalents for the simple case, and $(...) nests cleanly (unlike backticks, which need `cmd1 \`cmd2\`` escaping) when a substitution is needed inside another one.
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