No coverage tooling
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 coverage tool (jest/nyc/c8/coverage.py) was detected, so there's no visibility into how much of the code is actually tested.
Why it matters
Without a coverage report you cannot tell whether your tests exercise most of the code or five percent of it, so a passing suite carries little information. Coverage does not need to be a target number; its value is pointing at the untested files where the risky logic lives. That is usually where the next production bug is hiding.
How to fix it
Vitest and Jest have coverage built in: run vitest run --coverage (it uses @vitest/coverage-v8) or jest --coverage, or use c8 to wrap any Node test command. For Python, add pytest-cov and run pytest --cov, with configuration in a [tool.coverage] section of pyproject.toml. Put the coverage flag into your test script so every run reports it, add the output directory to .gitignore, and use the report to find untested critical paths rather than chasing a percentage.
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