Call graph

import/require graph · cycles · entry points and dead files · no heavy parser

부름 지도

zip 을 넣으면 파일이 서로 무엇을 부르는지 그리고, 고리·많이 불리는 파일·아무도 안 부르는 파일을 짚습니다

node_modules · dist · build · .git · coverage 는 건너뜁니다. 코드 파일(js·ts·jsx·tsx·css·vue·svelte)만 봅니다.

고리 (서로 부르는 자리)
많이 불리는 파일
아무도 안 부르는 파일
소스 zip 을 고르세요

Draws what calls what across your files, finds the cycles, and points at the most-called and the never-called ones — so you know where to start reading.

How to use it

  1. Drop in or paste several source files
  2. See the graph of what calls what
  3. Cycles (files that call each other) are marked as the knots to untie first
  4. Most-called = read first · never-called = an entry point or dead code

Common questions

Does it use a real parser?
No — too heavy. It finds import, require and export from as text, which is enough to answer "where do I start reading".
Why do cycles matter?
They hurt most when changing code. If A calls B and B calls A, whichever you read first leaves you blind.
Is my code uploaded anywhere?
No. Reading and drawing both finish inside your browser, so someone else’s repo is fine too.

Other tools

Stays on your device What you enter is handled inside your browser only — nothing is stored or sent anywhere.

This tool page states where what you enter goes — see the badge above. All tools · KarmoLab · Who made this · Built with AI. View source