I built Arbor because I kept running into the same problem: making a refactor and only discovering later that it broke something far away in the codebase.
Arbor analyzes a repository and builds a graph of functions, classes, and dependencies so you can preview the blast radius of a change before touching the code.
Example workflow:
git add .
arbor diff
This looks at modified symbols and shows impacted callers and dependencies.
Recent releases added:
• git-aware change analysis (`arbor diff`)
• CI safety checks (`arbor check`)
• incremental indexing
• persistent graph snapshots
• a small GUI for exploring impact
The goal is to make refactoring safer, especially when working in large codebases or when using AI coding tools.
I built Arbor because I kept running into the same problem: making a refactor and only discovering later that it broke something far away in the codebase.
Arbor analyzes a repository and builds a graph of functions, classes, and dependencies so you can preview the blast radius of a change before touching the code.
Example workflow:
This looks at modified symbols and shows impacted callers and dependencies.Recent releases added:
• git-aware change analysis (`arbor diff`) • CI safety checks (`arbor check`) • incremental indexing • persistent graph snapshots • a small GUI for exploring impact
The goal is to make refactoring safer, especially when working in large codebases or when using AI coding tools.
Repo: https://github.com/Anandb71/arbor
Would love feedback from people working on large or long-lived codebases.