Inconsistent semicolon usage
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 JS/TS file mixes semicolon-terminated and non-terminated statements, suggesting no formatter is enforced.
Why it matters
Mixed semicolon styles in one file are a symptom that no formatter runs, which is also how the genuinely dangerous inconsistencies (ASI hazards, like a line starting with a bracket after an unterminated statement) get in. It also breeds diff churn as contributors "fix" lines back and forth.
How to fix it
Pick one style and let a tool enforce it: Prettier with the semi option, or ESLint's semi rule with --fix. Run it over the file, then wire the formatter into CI or a pre-commit hook so the question never comes up again.
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