Dependency listed twice
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 same package appears in both dependencies and devDependencies in package.json.
Why it matters
When the same package sits in both dependencies and devDependencies, the two version ranges can disagree, and which one wins depends on your package manager. That makes installs behave differently across machines and makes it unclear whether production actually needs the package. It also trips up tools that prune devDependencies for production builds.
How to fix it
For each duplicated package, decide whether the running app imports it (dependencies) or only builds, tests, and tooling use it (devDependencies), then delete the other entry from package.json. Keep the stricter or more current version range on the surviving entry. Run npm install afterward so the lockfile is regenerated to match, and commit both files together.
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