No pre-commit hooks
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 pre-commit/husky configuration was found, so lint/test checks aren't enforced before code is committed.
Why it matters
Checks that only run in CI catch problems after the commit is already pushed, so broken or unformatted code still lands in history and the feedback loop is minutes instead of seconds. A pre-commit hook runs the cheap checks at commit time on just the files you touched. That keeps the main branch clean without anyone having to remember anything.
How to fix it
For JS/TS projects, use husky with lint-staged: npx husky init creates the hook, and lint-staged runs your linter and formatter over only the staged files so commits stay fast. For Python (or mixed repos), the pre-commit framework is the standard: commit a .pre-commit-config.yaml listing ruff and black hooks, then run pre-commit install. Keep hooks to fast checks measured in seconds; leave the full test suite to CI.
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