Summary
Twenty matches become the three that matter.
Ranking search hits by how central the surrounding module is turns an unfamiliar repository into something navigable — you start at the code everything else depends on rather than at whichever file sorted first.
What it is
A code search server that pairs ripgrep and symbol extraction with a PageRank-style ranking called CodeRank, so results arrive ordered by how central a module is to the codebase rather than by where the match happened to fall.
What you get
- Keyword search backed by ripgrep, with the number of context lines under your control
- Functions, classes, methods and modules extracted as symbols, filterable by type
- Usage tracking — where a symbol is referenced across the whole tree
- Search results ranked by code importance rather than by file order
- Dependency chains traced, including external module dependencies, for impact analysis
- Hotspots surfaced: the code that is both heavily connected and heavily used
- File include and exclude patterns, and analysis of Markdown documentation alongside source
Requirements
Python 3.13 or newer and the uv package manager, plus two command-line tools on the PATH: ripgrep for the text search and kit for symbol analysis. Without those two, the search and symbol sides have nothing underneath them.