scan → fix → finish → watch. One flow. No competing steps.
$ npm install -g arcsight $ arc scan
NEXT STEPS:
arc fix # apply safe fixes arc finish # resolve remaining issues arc watch # keep it clean (Pro)
Works with TypeScript · Node.js · Monorepos · Large codebases · CI pipelines
No code leaves your machine.
Find issues, apply fixes in seconds. Run arc scan, then arc fix.
Run in your repo
$ arc scanTry ArcSight:
Next step:
arc fix → preview or apply fixes instantlyArcSight finds issues and applies fixes so your architecture stays clean.
Modern codebases evolve faster than their architecture.
ArcSight automatically applies safe improvements and keeps your architecture clean.
As codebases grow, architecture becomes harder to reason about. Dependencies spread across modules and small changes can cause unexpected ripple effects.
Developers hesitate to refactor because they cannot easily predict what will break. Over time this leads to fragile systems and architectural drift.
ArcSight applies fixes instantly (arc fix) and keeps it clean (arc watch). No manual refactoring.
Improve your architecture in under 30 seconds.
Step 1
Install the CLI
npm install -g arcsightRun these commands from your project root.
Step 2
Scan for issues
arc scanStep 3
Apply safe fixes
arc fixStep 4
Finish remaining issues
arc finishStep 5
Keep clean (Pro)
arc watchOptional. Pro: continuous fixing.
ArcSight finds architectural issues and applies safe improvements — before changes break production.
Scan → Fix → Finish → Watch. Nothing else required.
arc scanFind issuesarc fixApply fixesarc finishResolve remainingarc watchKeep clean (Pro)Example output from running arc scan, then arc fix.
$ arc scan Scanning your codebase for architectural issues... Found 2 issues Run 'arc fix' to apply safe architectural improvements. $ arc fix Found 2 safe fixes in this run. Run arc fix to apply, or arc watch (Pro) to keep clean.
Works with
arc fixRun arc fix to preview or apply safe improvements. Pro: arc watch keeps your architecture clean.
ArcSight scans your dependency graph to reveal architectural risks, hotspots, and change impact before changes reach production.
ArcSight builds a dependency graph of your codebase to reveal hidden coupling, dependency cycles, and structural complexity.
Example CLI Output
$ arc analyzeDependency Graph Summary Modules analyzed: 184 Edges: 692 Cycles detected: 2 High fan-in modules: 6
This output highlights structural complexity and identifies cycles or highly connected modules that may introduce architectural risk.
ArcSight identifies modules with high fan-in — components that accumulate too many dependencies and become architectural bottlenecks.
Example CLI Output
$ arc hotspotsTop Fan-In Modules router/index.ts fan-in: 27 services/userService.ts fan-in: 19 utils/format.ts fan-in: 16
High fan-in modules often indicate architectural bottlenecks that make refactoring or scaling difficult.
ArcSight predicts which modules will be affected before refactoring or modifying core components.
Example CLI Output
$ arc impact services/paymentService.tsImpact Simulation Change target: services/paymentService.ts Affected modules: controllers/paymentController.ts jobs/paymentWorker.ts routes/paymentRoutes.ts
Impact analysis helps developers understand change risk before modifying core modules.
ArcSight helps developers find dependency risks, hotspots, and refactoring impact in modern codebases.
Typical ArcSight usage scenarios
Large React or Next.js codebases often accumulate shared utilities, routing layers, and cross-module dependencies that create hidden coupling.
arc hotspotsControllers, middleware, and service layers can create deep dependency chains that make refactoring risky.
arc scanService boundaries can hide long dependency chains that make architecture changes difficult without seeing change impact.
arc impact <module>Architecture analyses generated by the ArcSight CLI on real projects. Only architecture metrics and findings are shown.
Architecture Score: 89 / 100
ArcSight analyzed the Next.js framework package: 1,942 modules, 4,489 edges. Score 89/100 (A). Detected cycles, duplicate authorities, one layer violation, and critical choke points in types, config, and app-render.
View CLI analysis →Architecture Score: 84 / 100
ArcSight detected service modules with high centrality creating tight coupling between API layers.
View CLI analysis →Architecture Score: 71 / 100
ArcSight detected architectural drift and a utility module used across many packages creating change-impact risk.
View CLI analysis →Build a dependency graph, find issues, apply fixes instantly. Pro: done automatically, arc watch keeps it clean.
Find issues, apply fixes instantly. Pro: done automatically. Team & Enterprise: CI protection against drift.
scan → fix → finish → watch. One flow. Pro: arc watch keeps your architecture clean.
Run arc scan → arc fix → arc finish → arc watch. Pro: arc watch keeps your architecture clean.
Free: see what’s wrong, preview fixes. Pro: actually fix it—done automatically, keep it clean (arc watch). Safe to run, no manual refactoring. Team: protect in CI. Enterprise: enforce rules.
See what's wrong. Preview fixes.
Architecture visibility for individual developers and small projects.
$0
/ month
You're one step away. Apply these fixes instantly—no manual refactoring. Keep it clean with arc watch.
Architecture intelligence for developers.
$49
/ developer / month
Protect your architecture in CI
Continuous architecture protection for development teams.
$79
/ developer / month
Enforce architecture rules across teams
Organization-level architecture governance.
Join Waitlist
Upgrade to apply these fixes instantly (Pro)—one step away. Team: protect. Enterprise: govern. No risky changes.
Install the CLI, then run arc scan to find issues and arc fix to apply fixes in seconds.
npm install -g arcsightArcSight finds issues and applies fixes in seconds. Output matches what you see when you run arc scan and arc fix.
$ arc scan Scanning your codebase for architectural issues... Found 2 issues Run 'arc fix' to apply safe architectural improvements. $ arc fix Scanning your codebase for safe improvements... Found 2 safe fixes in this run: 1. Break dependency cycle — src/auth/AuthService.ts 2. Remove unused import — src/order/OrderService.ts These improvements reduce coupling and improve stability. Apply these fixes instantly with ArcSight Pro — no manual refactoring required. → https://arcsight.ai/pricing
Scan → fix → finish → watch.
Step 1
arc scanFind all issues in your codebase. No config required.
Step 2
arc fixApply safe fixes automatically. Safe to run—no manual refactoring.
Step 3
arc finishPlan or apply fixes for issues that need decisions. Use --apply or --copy for Cursor/LLM.
Step 4
arc watcharc watch applies fixes as they appear. No risky changes.
ArcSight helps developers understand and safely evolve large codebases.
ArcSight scans your codebase and builds a deterministic dependency graph. Scan runs on this graph to find dependency cycles, fan-in hotspots, architectural drift, and high-risk change paths.
No. The ArcSight CLI scans your code locally. Your source code never leaves your machine. ArcSight produces architecture metrics and fix suggestions without transmitting source files.
ArcSight currently supports TypeScript and Node.js codebases. Support for additional languages and ecosystems is planned.
ArcSight performs deterministic scanning rather than AI-based interpretation. The same codebase always produces the same dependency graph and results.
Yes. Team and Enterprise plans include CI architecture guards that find architectural regressions during pull requests and block risky changes before they reach production.
Found a bug, confusing output, or have an idea for improving ArcSight?
We're actively developing the tool and every piece of feedback helps us improve the scan and fix experience.