Monolithic entry point
Part of Architecture & Best Practices, which counts for 15% of the overall score. When this check fires it deducts 8 points from that category, once per scan, no matter how many places it turns up.
What it detects
The app's root entry file is very large, suggesting routes/logic/config were never split into modules.
Why it matters
When routes, config, and business logic all live in one giant entry file, every change touches the same file, merge conflicts multiply, and nothing can be tested in isolation. Bugs hide well in a several-hundred-line file with mixed concerns. Splitting it is mostly mechanical and pays off immediately.
How to fix it
Split by concern: routes into their own modules (express.Router in Node, APIRouter or Blueprint in FastAPI/Flask), config reading into a config module, database setup into its own file, and shared middleware into middleware files. Leave the entry point as thin wiring: import, register, listen. Extract incrementally with the app running so each step stays verifiable.
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