No linter configuration
Part of Testing & CI, which counts for 10% of the overall score. When this check fires it deducts 4 points from that category, once per scan, no matter how many places it turns up.
What it detects
No ESLint/Ruff/Flake8/Pylint configuration was found, so style and common bugs aren't checked automatically.
Why it matters
A linter catches real bugs before runtime: unused variables, unreachable branches, foot-gun patterns like loose equality in JS or mutable default arguments in Python. Without one, those problems surface only in code review or production, and a codebase edited by multiple people or AI agents drifts fast. It is the cheapest automated check you can add.
How to fix it
For JS/TS, add ESLint with typescript-eslint and commit a config file (.eslintrc.json is the widely recognized form), then add a "lint" script that runs eslint over your source. For Python, Ruff covers the flake8/pylint rule space at much higher speed: add a ruff.toml or a [tool.ruff] section in pyproject.toml and run ruff check. Fix the initial violations in one pass rather than disabling rules wholesale, then add the lint command to CI and any 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