Code Buster CLI
Code Buster finds dependency cycles, dead and duplicate code and complexity growth across a repository, locally and without an LLM
- 87 ★ on the repository
- Last commit
- MIT
Minimal access
Why this level
- Reads repository source locally, uploads nothing and changes no code files
Install
- Works in
Manual install
brew install tool-bunker/tap/code-busterApple Silicon macOS; for other systems `cargo install code-buster --locked` or the installers from the docs.
Access and checks
How we reviewMinimal accessThe tool runs nothing and makes no network calls.
- Reads repository source locally, uploads nothing and changes no code files
This is third-party code. Review the repository files before installing.
What it does
Code Buster is a Rust CLI that gives developers and coding agents deterministic feedback about a repository. It runs locally, uploads no source and calls no AI provider. File level rules combine with whole repository analysis. Findings cover dependency cycles and architecture policy 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. Each finding comes with evidence and remediation guidance. The `cb` command with no arguments checks the repository, while `cb review --pr`, `cb quality --structure`, `cb duplication` and `cb graph` run focused modes. Configuration is optional: `cb init` creates a commented starter, and `cb init rust`, `cb init bevy`, `cb init python` and `cb init typescript` give ready profiles. Rust, JavaScript, TypeScript, Python, Dart, Java, C#, C and C++, Go and Shell are supported.
Who it is for. Developers and teams on Rust, TypeScript, Python and Go who need cross-file analysis for review and for coding agents.
Good fit when
- An agent finished a large change and you need to see new dependency cycles and duplication before review
- A refactor goes in parts and you need unreachable code and complexity growth spots
- A pull request needs a check for architecture rule violations a linter does not see
- Source must not go to cloud services and the check must be deterministic
Not a fit when
- You want to replace the compiler, type checker or tests: Code Buster only complements them
- You need a blocking production quality gate: the project is pre 1.0, so evaluate findings first
- You need a vulnerability scanner over CVE databases: Code Buster has another job
Example request
Run cb review --pr for this branch and list new dependency cycles and duplicatesLimitations
- The project is pre 1.0, so evaluate findings and integrations before using it as a blocking CI gate.
- Findings are review signals and do not prove an error.
- Some languages are covered deeper than others, see the current matrix in the docs.
- The brew formula in the README is for Apple Silicon macOS, and for the rest there is `cargo install` and the installers in the docs.
- `cargo install` needs Rust 1.88 or newer.
How to disable. Delete the binary: `cargo uninstall code-buster` or `brew uninstall code-buster`. The repository configuration file is removed by hand.
FAQ
Does Code Buster send code to the cloud?
No. It runs locally, uploads no source and calls no AI provider.
How does it differ from a linter?
A linter looks at a file, while Code Buster adds whole repository analysis: cycles, duplicates, unreachable code and architecture policy violations.
How do I create a configuration?
With `cb init` for a commented starter or `cb init rust`, `cb init python`, `cb init typescript` for a ready profile.
Which languages does Code Buster support?
Rust, JavaScript, TypeScript, Python, Dart, Java, C#, C and C++, Go, Shell and others. The current table is in the docs.
Can it run as a pre-commit hook?
The repository has `.pre-commit-hooks.yaml`, and the integrations are described in the project docs.
Discussion
No questions or reviews yet.
Related
CLI toolsThree skills and a clippy config: an agent writes, reviews and ports idiomatic Rust, and CI enforces the checkable rules
A Rust MCP server and CLI with a call graph and hybrid semantic code search for Claude Code and Codex
A Rust CLI for TypeScript and JavaScript: dead code, duplicates, cycles, complexity and architecture boundaries from one graph, plus MCP and skills
codesearch searches code across several repositories with hybrid retrieval and runs fully offline, without a GPU or Docker.
CodeGraph (Rust)
codegraph-rust
A Rust code graph for agents: four MCP tools show what an edit will touch, how the architecture fits together and where the fragile spots are
inspect ranks Git changes by structural risk at the function and class level and serves the result to agents through JSON and MCP
Comparison with similar tools
Cards that share the main search query, and how they differ.
README in short
The README briefly explains what the tool does, gives install commands for macOS and Rust, the focused `cb` modes, the finding and language lists, the pre 1.0 limit and links to docs on install, commands, configuration, reports and integrations.