A tool similar t…
The entire repo summarised by code_analyze — structured JSON in <2k tokens. The dossier above is built from one call. Drill into specifics with code_search.
| File | Lines | Cx |
|---|---|---|
| processor/workers_test.go | 1,765 | 416 |
| processor/workers.go | 767 | 267 |
| main_test.go | 899 | 266 |
| processor/report_test.go | 773 | 237 |
| processor/formatters_test.go | 1,848 | 208 |
| config_test.go | 684 | 206 |
| processor/history.go | 615 | 175 |
| processor/processor.go | 692 | 173 |
| regression_test.go | 463 | 161 |
| processor/history_coupling.go | 699 | 159 |
| File | Lines | Cx |
|---|---|---|
| processor/constants.go | 15,120 | 0 |
| languages.json | 9,173 | 0 |
| processor/formatters_test.go | 1,848 | 208 |
| processor/workers_test.go | 1,765 | 416 |
| README.md | 1,334 | 0 |
| main_test.go | 899 | 266 |
| SCC-OUTPUT-REPORT.html | 808 | 0 |
| processor/report_test.go | 773 | 237 |
| processor/workers.go | 767 | 267 |
| processor/history_coupling.go | 699 | 159 |
Drop any public git URL or owner/repo shorthand.
Or compare boyter/scc against another repo:
Or use the API directly: curl https://api.searchcode.com/api/v1/code_analyze · Add to your MCP client