# fuzzy | Developer tool by Shubham Prakash

> Search any GitHub repository by name, typo or meaning. A Rust engine compiled to WebAssembly builds the index in your browser, so the code never leaves it.

Page: https://shubhamcodess.github.io/builds/fuzzy/

## fuzzy

Search any GitHub repository by name, typo or meaning. A Rust engine compiled to WebAssembly builds the index in your browser, so the code never leaves it.

- Page: https://shubhamcodess.github.io/builds/fuzzy/
- Kind: Developer tool, 2026
- Stack: Rust, WebAssembly, TypeScript, tree-sitter
- live: https://shubhamcodess.github.io/fuzzy/
- code: https://github.com/shubhamcodess/fuzzy

### Overview

Paste a repository such as `expressjs/express`. It splits the code into functions and builds a search index **in your browser**. Search by **keyword**, **typo** or **plain-English meaning**. There is no server, and the code **never leaves the browser**.

Measured:

- 139 KB: search engine, gzipped
- 0.8 ms: typo query, native benchmark on 11,839 chunks
- 14: languages chunked by tree-sitter

### What it does

- Keyword search that ignores case and word order: "parse config" finds parseConfig.
- Typo search: "reponse" finds response.
- Meaning search: "stop users who are not logged in".
- Results show the matching lines, and a saved index reopens without re-indexing.

### How it is built

- A Rust engine compiled to WebAssembly: an FST with edit distance 1 for typos, trigram bitmaps for substrings, BM25, HNSW for vectors and reciprocal rank fusion for hybrid results.
- tree-sitter keeps whole functions and classes together.
- Embeddings build in a worker, so keyword search works while they finish.

### Honest limits

- 3,000 files per repository and 200 KB per file. Keyword-only above 4,000 chunks.
- 60 GitHub requests an hour without a token.
- The benchmark runs natively and uses random vectors for the semantic part.

By Shubham Prakash: https://shubhamcodess.github.io/
