High performance code analysis tool written in Rust — stats, health scores, hotspots, trends, and cost estimation.
- Fast: Parallel file traversal, 30-50x faster than Python alternatives
- 65+ Languages: Built-in support for popular programming languages
- Smart Filtering: Respects
.gitignore, auto-excludes build directories - Multiple Outputs: Console, JSON, CSV, Markdown, HTML with charts
- Complexity Analysis: Function count, cyclomatic complexity, nesting depth
- Health Score: Project/directory/file-level health grading (A-F) with pluggable scoring models
- Hotspot Detection: Identify risky files via churn ×ばつ complexity analysis
- Trend Tracking: Save snapshots and compare codebase evolution over time
- Cost Estimation: Multi-model development cost estimation (COCOMO Basic/II, Putnam, LOCOMO)
- Extensible: Add custom languages via TOML configuration
brew install DropFan/tap/codelens
cargo install codelens
git clone https://github.com/DropFan/codelens
cd codelens
cargo build --release# Analyze current directory codelens # Analyze specific directories codelens src tests # Only count specific languages codelens -l rust,go,python # Output JSON codelens -f json -O stats.json # Output HTML report codelens -f html -O report.html # Show top 20 languages by code lines codelens --top 20 --sort code # Exclude directories codelens --exclude vendor,dist,node_modules # List supported languages codelens --list-languages
Score code health across five dimensions (complexity, function size, comment ratio, file size, nesting depth) with grades from A to F.
codelens health . # Project, directory, and file-level report codelens health . --top 20 # Show top 20 worst files codelens health . -f json # Output as JSON
Find the riskiest files by combining git change frequency (churn) with code complexity — files that change often AND are complex are the most likely sources of bugs.
codelens hotspot . # Last 90 days (default) codelens hotspot . --since 30d # Last 30 days codelens hotspot . --since 6m --top 5 # Last 6 months, top 5
Save snapshots and compare codebase evolution over time. Snapshots are stored in .codelens/snapshots/. Use latest, latest~N, or a date prefix like 2025年01月01日 as references.
codelens trend --save --label v1.0 # Save a labeled snapshot codelens trend # Compare latest two snapshots codelens trend --list # List all snapshots codelens trend --compare latest~2 latest # Compare specific snapshots
Estimate development cost, schedule, and team size using four pluggable models. Default mode runs all models and shows a comparison table.
codelens estimate . # All models comparison (default) codelens estimate . --model cocomo-basic # Single model with per-language breakdown codelens estimate . --model cocomo2 # COCOMO II Post-Architecture codelens estimate . --model putnam --ck 11000 # Putnam with custom productivity codelens estimate . --model locomo # LLM generation cost codelens estimate . --avg-wage 120000 # Custom salary across all models
| Model | Description | Reference | Typical Use |
|---|---|---|---|
| COCOMO Basic | Classic Boehm 1981 regression | Software Engineering Economics, Boehm 1981 (ISBN 0-13-822122-7) | Quick estimates, scc comparison |
| COCOMO II | Modern 2000 calibration with scale factors | Software Cost Estimation with COCOMO II, Boehm et al. 2000 (ISBN 0-13-026692-2) | Organization-level planning |
| Putnam/SLIM | Rayleigh-curve conservative model | A General Empirical Solution to the Macro Software Sizing and Estimating Problem, IEEE TSE 1978 | Risk assessment, worst case |
| LOCOMO | LLM token cost model | scc LOCOMO model, Boyter 2026 | AI-assisted development cost |
| Format | Flag | Description |
|---|---|---|
| Console | -f console |
Colored terminal output (default) |
| JSON | -f json |
Structured data for processing |
| CSV | -f csv |
Spreadsheet compatible |
| Markdown | -f markdown |
Documentation friendly |
| HTML | -f html |
Interactive report with charts |
Create .codelens.toml in your project root:
# Exclude patterns excludes = "*test*,*mock*" # Target languages lang = "rust,go,python" # Output format output = "json" # Threading threads = 8 # Depth limit depth = 10 # Show git info git_info = true
Note: This feature is planned but not yet implemented.
Custom language definitions will be supported in ~/.config/codelens/languages.toml:
[mylang] name = "MyLang" extensions = [".ml", ".mli"] line_comments = ["#"] block_comments = [["/*", "*/"]] function_pattern = "^\\s*def\\s+\\w+" complexity_keywords = ["if", "for", "while"]
MIT