Code Buster

Repository-aware static analysis for AI-assisted development.

Overview · Install · Docs · Contribute

Code Buster gives developers and coding agents deterministic feedback about a repository. It runs locally, does not upload source code, and does not call an AI provider.

Install

On Apple Silicon macOS:

brew install tool-bunker/tap/code-buster

With Rust 1.88 or newer:

cargo install code-buster --locked

The installation guide also covers native macOS, Linux, and Windows installers.

Run

From a repository root:

cb

Useful focused commands:

cb review --pr
cb quality --structure
cb duplication
cb graph
cb update

Configuration is optional. Run cb init for a commented starter configuration, or choose an opinionated profile such as cb init rust, cb init bevy, cb init python, or cb init typescript.

What it finds

Code Buster combines file-level rules with repository-wide analysis:

• dependency cycles and architecture violations;
• production dependencies on test code;
• duplicated and unreachable code;
• complexity growth and maintenance hotspots;
• correctness, security, accessibility, and performance risks;
• repository structure and framework drift.

Findings include evidence and remediation guidance. They are review signals, not proof that code is wrong.

Where it fits

Code Buster complements compilers, type checkers, linters, tests, formatters, and specialist security scanners. Use it for the repository-level and cross-file context those tools often do not cover.

It supports Rust, JavaScript, TypeScript, Python, Dart, Java, C#, C and C++, Go, Shell, and other languages. See the language matrix for current coverage.

Code Buster remains pre-1.0. Evaluate its findings and integrations before using it as a blocking production quality gate.

Documentation

• Quickstart
• Commands
• Configuration
• Reports
• Integrations

Development

cargo build --release --locked
./target/release/cb version

Read CONTRIBUTING.md for project structure, verification, and release instructions.