Excavate scans your JavaScript & TypeScript codebase analyzing git history, code complexity, coverage gaps, ownership risk, temporal coupling, and more. Get actionable insights in seconds.
Excavate combines multiple engineering signals into a single weighted technical debt score per file
Files that change too often become liabilities
Risky files without test safety net
Code that's hard to understand and maintain
Identifies files owned by too few people where knowledge leaves with one developer
Surfaces TODO, FIXME, HACK markers and low-comment areas needing attention
Detects files that change together, revealing hidden dependencies and tight coupling
Finds unused files that appear disconnected from the rest of the codebase
Discovers exported code that nothing imports, eliminating unnecessary bloat
Identifies circular dependencies, stale packages, and known CVEs
Your source code never leaves your machine. All analysis happens locally with zero external communication.
No network calls. No telemetry. No tracking. Your code stays completely private and never leaves your device.
All computation runs on your machine. No cloud dependencies. Perfect for regulated industries and sensitive codebases.
Open source MIT license. Inspect the code. No hidden data collection. Audit exactly what's happening.
A sophisticated multi-signal analysis engine that synthesizes engineering data into actionable insights
Excavate reads your git commit history and file blame data to understand how your codebase has evolved. This reveals files that change frequently (high churn) and who owns each piece of code.
The engine scans your code for complexity metrics, dependencies, exports, and code patterns. It builds a dependency graph to identify circular imports, dead exports, and orphan files.
Temporal coupling analysis reveals files that change together. Documentation analysis finds TODOs, FIXMEs, and HALFs. Ownership risk identifies single-person bottlenecks.
All signals are weighted and combined into a single debt score per file. High scores indicate files at highest risk of bugs, difficult to change, or close to knowledge loss.
Output a self-contained HTML report with interactive D3 treemaps, sortable data tables, trend charts, and LLM prompts to understand and refactor your highest-risk files.
No configuration files. No credentials. No servers. Just run npx excavate and start seeing your technical debt.
All analysis runs locally on your machine. No source code leaves your environment. No accounts. No internet required for core scanning.
Most tools show what your code looks like today. Excavate shows what your codebase has been struggling with over time, using git history and nine analysis signals.
Create beautiful, self-contained HTML reports with D3 treemaps, sortable tables, trend charts, and copyable LLM prompts for each file.
From startups to enterprises, teams use Excavate to understand and prioritize technical debt
Prioritize refactoring efforts, allocate resources to high-risk areas, and make data-driven technical decisions about where to invest.
Understand code organization risks, identify coupling patterns, discover orphan code, and plan refactoring roadmaps with confidence.
Run audits without leaving your network, generate compliance reports, identify knowledge risks, and maintain full code privacy.
Assess release risk, understand which files are prone to bugs, identify complex areas needing extra testing, and prevent incidents.
Powerful metrics from git history and code analysis combined into one risk score
Start analyzing your codebase today. It takes less than a minute.