Introduction

Weftmap turns your code into an interactive call graph. Paste a snippet or upload a project and see how functions, classes and modules relate.

What is Weftmap?

Weftmap reads your code with tree-sitter and draws a navigable map: who calls whom, which file imports which, and which class extends another. It never runs your code — it analyzes it statically.

What the graph shows

The nodes are the pieces of your code:

• Modules — each file, drawn as a container.
• Functions and methods — inside their module or class.
• Classes — group their methods.

The edges are the relationships:

• calls — one function calls another.
• imports — one module imports another.
• extends — one class extends another.

How to read it

• Drag to pan the canvas and scroll to zoom.
• The legend (top-left) toggles each edge type with a click.
• Boxes group things: modules contain classes and functions; classes contain their methods.

When to use it

• Onboarding to a new codebase and grasping its structure before reading line by line.
• Reviewing a PR by seeing how a function connects to the rest.
• Teaching or documenting by turning code into a diagram.

What it doesn't do

• It never runs your code or does dynamic analysis.
• It doesn't resolve dynamic/reflection calls, nor draw calls to external libraries.
• It's not a linter or type-checker — it only maps structure.