Will It Vibe?Wildcard import
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
A wildcard import (import pkg.*;) pulls in every public type from a package, which makes it unclear which types are actually used, invites name collisions as the package grows, and defeats some IDE/tooling analysis.
Why it matters
A wildcard import pulls in every public type from a package, so it is unclear from the import list alone which types the file actually depends on. It also invites silent name collisions as the package grows and can defeat some IDE refactoring and static-analysis tooling.
How to fix it
Expand the wildcard into explicit imports for only the types actually used in the file. Most IDEs can do this automatically (IntelliJ: Optimize Imports; Eclipse: Organize Imports).
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