Will It Vibe?Unused exported prop
Part of Code Quality & Syntax, which counts for 20% 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
An `export let` prop that is never referenced elsewhere in the component is dead API: it still shows up as an accepted prop, misleads callers, and is usually a leftover from a refactor. Heuristic: a prop consumed only through $$props or $$restProps can read as unused.
Why it matters
An export let prop that nothing in the component references is dead surface area. It still appears as an accepted prop, so callers pass a value that quietly goes nowhere, and readers waste time working out whether it matters. It is usually a leftover from a refactor. This is a heuristic: a prop consumed only through $$props or $$restProps can look unused.
How to fix it
If the prop is truly unused, delete the export let line and remove it from callers. If it was meant to be used, wire it into the markup or logic. If it exists only to be forwarded, forward it explicitly or document that it is part of $$restProps. Check the callers before deleting so you do not silently drop something a parent still passes.
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