Kanota

Impact Analysis Dashboard for JavaScript/TypeScript Codebases

Kanota answers the question: "If I change this file, what might break?"

It uses static analysis (AST + import graph) to calculate risk scores and visualize the blast radius of changes in your codebase.

Quick Start

cd your-project
npx kanota

That's it! Kanota will:

1. Scan your project for JS/TS/Vue/Svelte files
2. Build a dependency graph
3. Calculate risk scores for each file
4. Open an interactive dashboard in your browser

Features

• Risk Scoring: Files are scored based on dependents, entry points, shared modules, and file size
• Blast Radius Visualization: See exactly what might break if you change a file
• Actionable Guidance: Get specific recommendations like "Clone logic instead of editing directly"
• Entry Point Detection: Automatically identifies pages, layouts, and routes (Next.js, Vue, Svelte, Angular)
• Shared Module Detection: Flags files in /components, /hooks, /utils, /lib folders

Dashboard Views

Guided Decisions

• Top velocity blockers
• Safest refactors this week
• Files to stabilize before scaling

Risk Analysis

• Filter by risk level (High / Medium / Low)
• Click any file to see its impact
• View direct dependents and transitive affected files

Project Details

• File count, lines of code, import links
• Entry points and shared modules overview

Supported File Types

• .js, .jsx, .ts, .tsx
• .mjs, .cjs, .mts, .cts
• .vue, .svelte

How Risk is Calculated

| Factor | Weight | |--------|--------| | Dependents count | +3 per dependent | | Entry point (page/layout/route) | +5 | | Shared folder (/components, /hooks, etc.) | +3 | | Large file (>300 lines) | +2 |

Risk Levels:

• Low: Score ≤ 3
• Medium: Score 4-7
• High: Score > 7

Options

# Analyze current directory
npx kanota

# Analyze a specific directory
npx kanota /path/to/project

# Use a custom port
KANOTA_PORT=4000 npx kanota

License

MIT