See what deserves a refactor.
See the evidence first.
Reforge analyzes the structure of a codebase, explains every finding, and makes gaps in analysis visible.
reforge analyze . --output html --output-file reforge-report.html
From signal to decision
Reforge does not hide structural observations behind a score. It gives reviewers the context needed to decide whether a change is worthwhile.
Find the pressure points
Surface duplication, oversized responsibilities, dependency tangles, naming drift, and difficult value paths.
Inspect the evidence
Trace each finding back to its rule, measurements, source locations, and exact value-flow witness when available.
Know the limits
See partial and unsupported analysis explicitly. No findings never means more coverage than Reforge actually observed.
What Codebase looks for
Responsibilities
Find oversized files, functions, types, public surfaces, and directories that may own too much.
Duplication and drift
Inspect repeated implementations, overlapping shapes, generic buckets, naming drift, and dependency tangles.
See how Codebase analysis works →
Designed for review, not scoring
Findings are inspection prompts—not severity labels, priorities, or defect predictions. Reforge runs locally, uploads no source code, and collects no telemetry. Use it interactively, generate a standalone HTML report, or compare reviewed JSON baselines in CI. An advanced Dataflow analysis is available when exact value-path inspection is needed, but it is not required for normal Codebase use.