ARCLUX ๐Ÿณ โ€“ ์ฝ”๋“œ๋ฒ ์ด์Šค์— ๋Œ€ํ•œ ์ข…์†์„ฑ ๊ทธ๋ž˜ํ”„ ๋ฐ ์˜ํ–ฅ ๋ถ„์„

์ž‘์„ฑ์ž

์นดํ…Œ๊ณ ๋ฆฌ:

โ† ํ”ผ๋“œ๋กœ
DEV Community ยท Mikatoshi ยท 2026-08-09 ๊ฐœ๋ฐœ(SW)

Mikatoshi

OPEN SOURCE๐Ÿ‘‡

I’ve been building ARCLUX โ€” a repository intelligence tool (CLI + web dashboard) that maps your codebase into a dependency graph, traces impact (“what breaks if I touch this file?”), and runs 18 structural detectors (circular deps, dead code, orphan files, layer violations, etc).

Verified at meaningful scale โ€” microsoft/vscode, facebook/react, and vitejs/vite all analyze successfully, not just small toy fixtures.

Language support:

  • TypeScript, JavaScript, Python โ€” full support
  • Go, Java โ€” parsing works, but same-package calls with no import statement (common in both languages) aren’t resolved as edges yet

Honest state (this is v0.1.0-alpha):

  • Very large/unusual repos (10k+ files, heavy monorepos) can currently time out or fail without a clear error โ€” no size guard or progress streaming yet, that’s next
  • Some packages (search, persistent caching) are still stubs

I’m not trying to compete with enterprise tooling โ€” this started as a personal project to actually understand codebases I work in, and it grew from there.

Would love feedback, bug reports, or PRs if any of this is useful to you.

์›๋ฌธ์—์„œ ๊ณ„์† โ†—

์ถ”์ถœ ๋ณธ๋ฌธ ยท ์ถœ์ฒ˜: dev.to ยท https://dev.to/mikatoshi/arclux-dependency-graph-impact-analysis-for-your-codebase-mi

์ฝ”๋ฉ˜ํŠธ

๋‹ต๊ธ€ ๋‚จ๊ธฐ๊ธฐ

์ด๋ฉ”์ผ ์ฃผ์†Œ๋Š” ๊ณต๊ฐœ๋˜์ง€ ์•Š์Šต๋‹ˆ๋‹ค. ํ•„์ˆ˜ ํ•„๋“œ๋Š” *๋กœ ํ‘œ์‹œ๋ฉ๋‹ˆ๋‹ค