No .editorconfig
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 .editorconfig file was found to keep indentation/charset/line-ending conventions consistent across editors.
Why it matters
Editors default to different indentation, line endings, and trailing-whitespace behavior, so a team on mixed setups (or one person on two machines) produces noisy diffs and the occasional CRLF surprise in a shell script. An .editorconfig file fixes those defaults per repo and nearly every editor honors it without a plugin. It is a two-minute change that quietly prevents recurring diff noise.
How to fix it
Create .editorconfig at the repo root with root = true, then a [*] section setting charset = utf-8, end_of_line = lf, insert_final_newline = true, trim_trailing_whitespace = true, and the indent style and size your code already uses. Add narrow overrides where conventions differ, such as tabs for Makefiles or keeping trailing whitespace in Markdown. Match the existing codebase rather than introducing a new style, and let your formatter stay the authority where the two overlap.
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