Will It Vibe?Wildcard import
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
from module import * pulls every public name into the current namespace without saying which ones, and can silently shadow existing names.
Why it matters
from module import * pulls every public name from that module into the current namespace without saying which ones, so readers, linters, and IDEs cannot tell where a given name actually came from. It also risks silently overwriting names already defined in the current file, since a later wildcard import can shadow a function or variable with the same name from the imported module without any warning.
How to fix it
Import only the specific names the file actually uses, for example from module import func_a, func_b, or import the module and reference names through it (import module, then module.func_a()). Most editors can generate the explicit import list automatically from the names already used in the file.
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