Will It Vibe?Component <style> is not scoped
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
A single-file component defines a <style> block with neither scoped nor module, so its rules are global and can leak into unrelated components. Heuristic: a deliberate global stylesheet is a valid exception, so severity is low.
Why it matters
A <style> block without scoped or module emits plain global CSS. Its selectors apply across the whole app, so a rule meant for one component can restyle or break unrelated ones, and later components can accidentally override it. In a large app this makes styling changes risky because their blast radius is the entire page. This is a heuristic: a deliberately global base stylesheet is a legitimate exception.
How to fix it
Add the scoped attribute to component <style> blocks so styles apply only to that component, or use <style module> and bind classes through $style when you want locally scoped class names. Keep genuinely global styles (resets, design tokens) in one clearly named entry stylesheet rather than spread across component files.
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