FlowMap

PUBLIC BETA NOTICE (March 8, 2026): FlowMap is in public beta. Licensing is currently local/dev-only preview (no production server-side entitlement enforcement yet).

FlowMap

Swift code graph and impact analysis tool — understand and verify code structure, especially when reviewing AI-generated changes.

CI

한국어 · 日本語

What is FlowMap?

FlowMap parses Swift code, builds a workspace-level graph of files, types, functions, and call relationships, and visualizes that graph inside VS Code.

It answers questions like:

FlowMap is not a compiler replacement. It makes real code structure visible at the workspace level so you can verify relationships directly rather than inferring them.

Why JavaScript is the largest language share

GitHub language percentages reflect implementation layers, not analysis target language.

FlowMap still targets Swift codebases; the JS-heavy ratio comes from editor/runtime integration.

Who it is for

Current features

Cross-file call-linking boundaries (current beta)

FlowMap intentionally resolves cross-file calls conservatively to reduce false links. This means some dynamic/indirect patterns are represented at interface level rather than concrete implementation level.

This behavior is expected in current public beta and is being expanded incrementally.

Screenshots

Overview mode

Overview mode

File detail mode

File detail mode

Calls mode

Calls mode

Installation

Prerequisites

Platform note: Linux/Windows are not supported yet because the current Swift parser build/runtime path depends on macOS Swift toolchain assumptions.

Build

1. Clone the repository

git clone https://github.com/adgk2349/FlowMap-AI_Code_Hallucination_Guard_for_Swift.git FlowMap
cd FlowMap

2. Build the Rust engine

cargo build

3. Build the Swift parser

cd parsers/swift-ast
swift build -c release
cd ../..

Note: replay/scenario validation scripts look for the parser binary at parsers/swift-ast/.build/debug/flowmap-swift-ast.
If you run those scripts, also build debug once: cd parsers/swift-ast && swift build -c debug.

4. Compile the VS Code extension

cd editor/vscode
npm install
npm run compile
cd ../..

Run in VS Code

  1. Open the editor/vscode folder in VS Code
  2. Press F5 to launch the Extension Development Host
  3. In the new VS Code window, open a Swift workspace
  4. Run FlowMap: Analyze Workspace from the command palette (Cmd+Shift+P)
  5. Open the FlowMap Graph panel

Run from VSIX (installed extension)

If you install FlowMap via .vsix, set flowmap.binaryPath to your built engine binary path (for example: /path/to/FlowMap/target/debug/flowmap), then run FlowMap: Analyze Workspace.

Usage

  1. Open a Swift workspace in VS Code
  2. Run FlowMap: Analyze Workspace via the command palette
  3. Explore the graph:
    • Overview — browse project structure at a glance
    • File Detail — click into a file to inspect its types and functions
    • Calls — trace call clusters and follow how functions connect
  4. Save a file to trigger automatic re-analysis

Validation

FlowMap includes automated replay validation that replays real Git commit pairs and checks whether graph diff changes are detected in the expected direction.

Example:

node scripts/run_commit_replay.mjs \
  --repo /path/to/swift-repo \
  --count 100 \
  --report reports/replay-100.json

Current bundled validation output:

Latest bundled metrics (reports/replay-validation-bundle.md):

Latest scenario regression (reports/sample-scenarios-report.json):

Detailed public beta validation (reports/public-beta-validation-detail.md):

License

FlowMap is currently in public beta.

Final licensing terms (including commercial terms) will be announced after the beta period.

Until then, all rights are reserved by the author, except that evaluation use for the public beta is permitted.

For commercial use or redistribution, please contact: adgk2349b@gmail.com

Roadmap

Contributing

Issues and pull requests are welcome.

Good areas to contribute:

Status

FlowMap is now in Public Beta.