Repository Intelligence
Git-History Risk Scoring
Weight risk by how often a file actually changes and how many people touch it, not just its static complexity. Paste a real GitHub repo to see it.
This is one question. ArchSetu answers it for a whole repository.
Call graph, dead code, blast radius and a health score, in about a minute.
Related tools
All Repository Intelligence tools →Dependency Graph VisualizerPaste package.json - dependencies grouped by type, plus packages listed twice with conflicting versions.Blast Radius ExplorerPaste a real GitHub repo, pick a file, see exactly what breaks if you change it - the real reverse-dependency graph.Dead Code FinderPaste a real GitHub repo - functions with zero known callers, traced from the real call graph.Dependency Hygiene CheckerPaste a real GitHub repo - packages imported in code but never declared in any package.json.Cargo.toml Dependency AuditorPaste Cargo.toml - every dependency listed, with wildcard or bare-major version ranges flagged.Cyclomatic Complexity CalculatorPaste one function - get its cyclomatic complexity score, the same signal behind Repository Analysis.
Was this tool helpful?