Hey I'm Raj, solo founder of N3MO. This started from a failed GSoC attempt I couldn't navigate a large renamed function in an open-source codebase and had no way to see what else would break if I touched it. That frustration became N3MO. N3MO is a deterministic, AST-based code intelligence engine. It parses your codebase with Tree-sitter and builds a call graph in PostgreSQL no embeddings, no LLM calls, no hallucination risk. When you open a PR, N3MO posts a blast-radius report in under 2 seconds showing exactly which downstream components a change will affect. A few things that might be useful to know: Free CLI (pip install n3mo) already at 8k daily active users GitHub App for automatic PR impact reports MCP server so Claude, Cursor, and other agents get a real dependency graph instead of raw file chunks or guesses Benchmarked on TensorFlow (480k+ call edges, ~14 min cold index) and Django (~9x faster after optimization) Would love your feedback sespecially from anyone who's been burned by a "should be safe" refactor that wasn't. Happy to answer anything about the architecture, pricing, or roadmap in the comments.

N3MO – See What Breaks Before You Merge

Deterministic PR impact reports in under 2 seconds

Deterministic PR impact reports in under 2 seconds