Practical overview
When it fits
Use SolFlow during repository review when you need a navigable view of call paths from external entry points, alongside source code. The target project must build in its own directory for Slither to analyze it.
Who it is for
- Web3 security auditors tracing contract execution paths
- Solidity developers reviewing how externally callable functions reach code across contracts, libraries and modifiers
Documented uses
- Browse externally callable functions grouped by contract and by mutating or read-only behavior.
- Expand a call tree and inspect the source at each function node and call site.
- Adjust analysis scope by excluding paths or contracts, inlining selected libraries, or stubbing selected targets.
- Bind an interface call to a concrete implementation while keeping the binding identifiable as an assumption.
Requirements & limits
The documented workflow uses a Python CLI and serves the interface locally at 127.0.0.1. The repository identifies the license as AGPL-3.0.
- Requires Python 3.11 or later and a solc version matching the target project, managed with solc-select.
- The project must already build with its dependencies resolved; SolFlow does not install dependencies or modify the repository.
- Slither and crytic-compile underpin analysis, so compilation or analysis limitations prevent visualization.
- Calls that cannot be resolved statically are marked; a manually bound implementation is an asserted assumption, not proof.
- The tool visualizes code structure but does not scan for vulnerabilities or produce findings.
Check current requirements in the official documentation. Source-based guidance does not mean OpenViST has run or independently tested this project.
Install SolFlow and its Solidity compiler manager
Set up the documented command-line prerequisites for analyzing a Solidity repository.
Before you start
- Python 3.11 or later
- pipx
Steps
Install SolFlow with
pipx install solflow.Install the compiler manager with
pipx install solc-select.Install and select a solc version matching the target project's Solidity pragma using
solc-select install && solc-select use.
Expected outcome
SolFlow and solc-select are installed, with a Solidity compiler version selected for the target project.
Guide limitations
- This setup does not install the target project's dependencies or confirm that the project builds.
- SolFlow cannot visualize a project that Slither cannot compile and analyze.
Open call-flow visualizations for a Solidity project
Start SolFlow on a repository and open its locally served entry-point Flows.
Before you start
- SolFlow and a matching solc version
- A Solidity project that builds in its own directory, with dependencies resolved
Steps
From the project environment, run
solflow path/to/your/solidity/project, pointing to the repository root.Open the local URL printed by SolFlow.
Browse the entry-point index and expand a Flow to inspect its call tree and source.
Expected outcome
The local interface serves navigable call-flow graphs for the repository's analyzed external entry points.
Guide limitations
- SolFlow does not install dependencies or modify the target repository to make it build.
- Unresolvable call targets are marked rather than inferred; interface bindings are asserted assumptions, not static proof.
- The tool emits no vulnerability findings and makes no security claims.
Sources & review
Source record details
- Source availability
- Active
- Sources checked
- 14 October 2026
- Original website title
- norah1499/solidity-flow-navigator · Official homepage title · retained in its source language