DevMapProduct · Review
Findings come with evidence.
Review reads a workspace’s files and reports what it can prove, what it only suspects, and what it could not check.
Confidence
Three levels, never blurred.
A finding’s confidence tells you how much to trust it.
- Confirmed
- Provable from the files: a broken relative import, a syntax error, an import cycle, byte-identical duplicates.
- Candidate
- Likely but not proven: unused files and exports, undeclared dependencies. Evidence lists what was checked and what could hide a use, such as dynamic imports.
- Suggestion
- Worth considering, with no claim that anything is wrong.
How it works
From finding to approved change.
Run Review on a workspace
DevMap builds an import graph for JavaScript, TypeScript and Python using only the files on disk. It does not run your code.
Triage
Filter by severity, category, confidence or status, scope to a folder or file, and mark findings reviewed or dismissed, singly or in bulk.
Read the evidence
Each finding shows where it is, why it was reported and a suggested next step, plus the limits of the analysis.
Act, with approval
Open the file, show it in the Map or Files, or move candidates to the Trash. Anything that changes files goes through a plan you approve first.
When it helps
After a refactor.
A moved file leaves behind a broken relative import. Review reports it as confirmed, with the file and line, so you fix the cause rather than find it at runtime.
Review does not analyse imports in other languages, dynamic imports, test coverage or near-duplicate code, and it lists these limits with each run. Separately, a Checks tab can run a project’s own test, lint or build commands, but only when you ask.