No formatter configuration
Part of Testing & CI, which counts for 10% 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
No Prettier/Black configuration was found, so code style likely drifts across contributors and AI-assisted edits.
Why it matters
Without a shared formatter, every contributor and every AI edit brings its own spacing and quote style, so diffs fill with formatting noise and review attention goes to whitespace instead of logic. A formatter makes every diff show only the real change. It also removes an entire category of nitpick from code review.
How to fix it
For JS/TS, add Prettier: commit a .prettierrc (even an empty {} object works, the defaults are fine) and a "format" script. For Python, add Black via a [tool.black] section in pyproject.toml. Run the formatter across the whole repo once in a dedicated commit so future diffs stay clean, then enforce it with a check mode command (prettier --check, black --check) in CI or a pre-commit hook.
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