Plannotator: a map of its code, package by package.

Plannotator is the workspace for shaping and reviewing the plans of coding agents. Wingbox built the graph of the repository, with no model, and the map stacks its code by package: 2,802 files and 10,296 dependencies on 24 planes, the packages the others depend on lower. Click a file to see what a change to it reaches.

Plannotator on 24 package planes, one file selected with its blast radius
Open the live mapRead the reportbacknotprop/plannotatorDrag to turn the planes, scroll to zoom, click a file for its blast radius.
The report

What Wingbox wrote on the whole repository

REPORT.md as the tool wrote it, without its own guesses of architecture layers.

Wingbox report: plannotator

Generated on 2026-11-16 by wingbox 0.2.6 from the code graph of this project. Open map.html in this folder for the interactive map.

Key findings

  • A change to packages/core/inbox-types.ts reaches 1,763 of 5,662 modules (31%) within 2 hops; 1,096 modules depend on it directly.

Summary

Modules5,662
Dependencies between modules18,878
Functions, constants, classes and types55,870
Languagests 4,131, tsx 1,492, js 25, py 14
Boundary violations6

Most depended-on modules

A change in one of these files reaches the most code (test files are left out). "Within 2 hops" counts the modules that depend on it directly or through one other module.

FileDirect dependentsWithin 2 hops
packages/core/inbox-types.ts1,0961,763
packages/ui/types.ts362802
packages/inbox/api.ts310713
packages/inbox/icons.tsx224625
packages/server/inbox.ts208216
scripts/inbox-sim.ts207224
packages/shared/inbox/store.ts195424
packages/shared/inbox/connection.ts177790
packages/ui/utils/storage.ts177450
packages/shared/inbox/schema.ts131571
packages/ui/utils/parser.ts113355
packages/inbox/shell/sidebar.tsx108152
packages/core/question-block.ts1021,721
packages/inbox/format.ts96538
packages/inbox/components/Tip.tsx95458

Where to start reading

Files that nothing else depends on and that pull in the most modules:

  • apps/hook/server/index.ts, depends on 99 modules
  • packages/references/src/index.ts, depends on 16 modules
  • packages/ui/components/diagram/index.ts, depends on 13 modules
  • apps/guides-show/viewer/main.tsx, depends on 12 modules
  • apps/vscode-extension/src/guides/reader/main.tsx, depends on 10 modules
  • apps/vscode-extension/src/guides/webview/main.ts, depends on 7 modules
  • packages/inbox/guide/PlatformPost.tsx, depends on 7 modules
  • scripts/launch-smoke/claude.ts, depends on 6 modules
  • scripts/launch-smoke/day1.ts, depends on 6 modules
  • scripts/launch-smoke/permission.ts, depends on 6 modules

Next steps

Check what a change will reach before you make it:

wingbox impact packages/core/inbox-types.ts

Rebuild after the code changes with wingbox build. This report and the map are rewritten on every build.

Limits

The graph comes from static parsing. Dependencies created at run time (dependency injection, reflection, generated code) are not visible here.

Method

How this was made

  • Wingbox 0.2.6 from PyPI on the whole repository at commit 3456b94, 2026-11-16: one command, wingbox build .
  • The map leaves out the 2,860 test files and puts every other file on the plane of its package, the folder of its nearest package manifest. The planes are stacked by the dependencies between packages.
  • Checked against the code. TypeScript and JavaScript dependencies compared with an import resolver written apart from Wingbox: 18,874 in the graph, 18,875 found by the resolver, 18,872 in both. The two more in the graph are subpath imports of a workspace package the resolver does not follow; the three only in the resolver are imports with a Vite query suffix (?worker&inline, ?api-404-guard). Python dependencies compared with Python's own parser: 4 in the graph, 4 imports in the code, 0 missing, none extra.

Run it on any repository: pipx install wingbox && wingbox build . · Wingbox on GitHub (MIT)