Download Code Buster

Code Buster — Free Download. Repository analyzer

Code Buster is not positioned as a replacement for linters such as dart analyze, ESLint, Clang-Tidy, or compiler diagnostics. It works alongside those tools. A linter usually focuses on one language and local code issues. Code Buster steps back and looks at the repository as a whole. It reports connections between modules, the likely impact of a change, duplicated logic that is starting to drift, parts of the repository that need attention, and bypasses of existing boundaries, components, or design tokens. The output is intended for maintainers, tech leads, and coding agents rather than as a line-by-line style gate.

★★★★★
5.0(1 ratings)
Version: 0.3.0
Size: 4.32 MB
Systems: Windows, Mac OS, Linux

Code Buster scans an entire repository with a single command. It maps dependencies between files and modules, finds cycles that block clean architecture, and flags code that no longer has any reachable reference. The analyzer measures duplication across token sequences and structural hashes, separating exact copies from near-miss drift. Complexity metrics identify functions and methods with dangerous branching density, nesting depth, or parameter load. Architecture policies let teams define forbidden imports and immediately see when a boundary is crossed.

The tool audits feature flags for staleness and measures the code path hidden behind each toggle. Security heuristics detect dangerous API calls, weak crypto defaults, dynamic includes, path traversal, and hard-coded secrets, with severity adjusted by reachability. Style heuristics look at repository-level conventions such as naming consistency, file size outliers, and import ordering anomalies. All of these inputs combine into a quality score that can be tracked per directory, per package, or across the whole codebase.

Code Buster produces remediation plans that group related findings into prioritized work items. Each item lists the affected files, violated rule, suggested change, and estimated effort. The plan is ordered by impact and risk, filtering out low-value cleanup when active feature work would be disrupted. Historical quality snapshots allow teams to compare scores over time and trace regressions to specific commits. The tool self-analyzes its own source during every release, which keeps the rules aligned with real code and catches analyzer regressions before they ship.

Use Cases for Code Buster

Maps how files import and reference each other Traces change impact across all dependent modules
Finds unreferenced files, functions, classes, constants, exports Separates confirmed dead code from test only references
Scans module graph for directed circular dependencies Reports shortest cycle path and participating files
Compares token sequences and structural hashes Detects exact, near miss, and drifted duplicates
Scores cyclomatic complexity, nesting, cognitive load Cross references hotspots with dependency frequency
Validates imports against user defined dependency rules Groups violations by rule for root fixes
Locates feature flag references and conditional branches Reports stale flags removed from config but still coded
Scans dangerous calls, weak crypto, hardcoded secrets Prioritizes findings by reachability from entry points
Checks naming, file size, nesting, import conventions Compares files against own directory style
Aggregates all metrics into single 0 to 100 score Produces per directory scores for regression tracking
Emits prioritized actionable remediation work items Machine readable for issue tracker import
Default summary combines all major report categories Readable in under a minute, terminal or JSON