High TODO/FIXME density
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
More than 1 TODO/FIXME/HACK marker per 100 lines suggests unfinished work shipped as-is.
Why it matters
This flags files carrying more than one TODO/FIXME/HACK marker per hundred lines, which means the file's known gaps shipped with it. Users then hit exactly the cases the markers describe, and since the notes live only in source comments, nobody is tracking or prioritizing them.
How to fix it
Triage each marker: fix the quick ones now, move real future work into your issue tracker and replace the marker with a reference or delete it, and remove stale markers that no longer apply. If you want to keep markers out permanently, enable ESLint no-warning-comments or Ruff's FIX rules.
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