Node engines mismatch
Part of Dependencies & Hygiene, 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
The declared Node engine version is older than what the syntax used in the code actually requires.
Why it matters
Your package.json says the project runs on an old Node line (10 to 12), but the code uses optional chaining or nullish coalescing, which need Node 14 or newer. Anyone who trusts the engines field and installs that Node version gets SyntaxError crashes at startup. Deploy platforms and version managers that read this field will happily provision the broken version for you.
How to fix it
Update the engines.node field in package.json to a version the code actually supports, realistically ">=18" or ">=20" since Node 14 and 16 are already end-of-life. Update .nvmrc and any CI node-version settings to match so local, CI, and production agree. If you need the strict check, npm can enforce engines with engines-strict in .npmrc.
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