Mixed line endings
Part of Dependencies & Hygiene, 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
A file mixes Windows (CRLF) and Unix (LF) line endings, which shows up as noisy diffs.
Why it matters
A file that mixes CRLF and LF endings makes diffs and blame noisy, because editors and git keep "correcting" lines back and forth and every save can touch lines nobody edited. It also breaks line-sensitive files, like shell scripts with CRLF, in confusing ways. Normalizing once and enforcing it in git config stops the churn.
How to fix it
Normalize the flagged files to LF (any editor can convert, or run a small script), then stop it recurring: add a .gitattributes with "* text=auto eol=lf" so git normalizes text files on commit, and an .editorconfig with end_of_line = lf so editors agree. If you use Prettier, its default endOfLine: "lf" enforces the same thing on format. Windows contributors keep working normally; git handles the conversion at the boundary.
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