No type-checking configuration
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 TypeScript config or mypy configuration was found for a project that would benefit from static type checking.
Why it matters
This project depends on TypeScript but has no tsconfig.json, or is a Python project with no mypy setup, which means the type checker either never runs or runs with loose defaults while editors guess at settings. Type annotations that are never checked drift out of date and give false reassurance. A configured checker turns whole classes of bugs (typos, wrong argument shapes, forgotten null cases) into editor squiggles instead of runtime errors.
How to fix it
For TypeScript, create a tsconfig.json (npx tsc --init is a fine start) with strict: true, noEmit: true if a bundler does the actual build, and module settings that match your toolchain, then add a "typecheck": "tsc --noEmit" script and run it in CI. For Python, add a [tool.mypy] section to pyproject.toml (or an mypy.ini), starting permissive with ignore_missing_imports = true and tightening per module over time. Either way, get the checker to a clean exit once, then keep it clean.
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