Repository Intelligence
Technical Debt Interest Estimator
Estimate the recurring time cost of a workaround, and how many months until fixing it properly would have paid for itself.
/month
hrs
hrs (one-time)
Payback period
Fixing this properly pays for itself in 2.7 months
Beyond this point, leaving it unfixed costs more than the one-time fix would have.
Monthly "interest" paid6.0 hrs/month
One-time fix cost16.0 hrs
Payback period2.7 months
Monthly interest = touches/month × extra hours per touch. Payback period = hours to fix properly ÷ monthly interest hours. A rough estimation aid, not an exact accounting figure.
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.Git-History Risk ScoringPaste a real GitHub repo - bus factor and ownership risk from its actual commit history, not a paste-one-file estimate.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.
Was this tool helpful?