code2flow
AI Cost Tracking
- 🤖 LLM usage: $13.0434 (125 commits)
- 👤 Human dev: ~$6497 (65.0h @ $100/h, 30min dedup)
Generated on 2026-07-29 using openrouter/qwen/qwen3-coder-next
Python Code Flow Analysis Tool - Static analysis for control flow graphs (CFG), data flow graphs (DFG), and call graph extraction.
Performance Optimization
For large projects (>1000 functions), use Fast Mode:
# Ultra-fast analysis (5-10x faster)
code2flow /path/to/project --fast
# Custom performance settings
code2flow /path/to/project \
--parallel-workers 8 \
--max-depth 3 \
--skip-data-flow \
--cache-dir ./.cache
Performance Tips
| Technique | Speedup | Use Case |
|---|---|---|
--fast mode |
5-10x | Initial exploration |
| Parallel workers | 2-4x | Multi-core machines |
| Caching | 3-5x | Repeated analysis |
| Depth limiting | 2-3x | Large codebases |
| Skip private methods | 1.5-2x | Public API analysis |
Benchmarks
| Project Size | Functions | Time (fast) | Time (full) |
|---|---|---|---|
| Small (<100) | ~50 | 0.5s | 2s |
| Medium (1K) | ~500 | 3s | 15s |
| Large (10K) | ~2000 | 15s | 120s |
Features
- Control Flow Graph (CFG): Extract execution paths from Python AST
- Data Flow Graph (DFG): Track variable definitions and dependencies
- Call Graph Analysis: Map function calls and dependencies
- Pattern Detection: Identify design patterns (state machines, factories, recursion)
- Compact Output: Deduplicated flow diagrams with pattern recognition
- Multiple Output Formats: YAML, JSON, Mermaid diagrams, PNG visualizations
- LLM-Ready Output: Generate prompts for reverse engineering
Installation
# Install from source
pip install -e .
# Or with development dependencies
pip install -e ".[dev]"
Quick Start
# Analyze a Python project
code2flow /path/to/project
# With verbose output
code2flow /path/to/project -v
# Specify output directory and formats
code2flow /path/to/project -o ./analysis --format yaml,json,mermaid,png
# Use different analysis modes
code2flow /path/to/project -m static # Fast static analysis only
code2flow /path/to/project -m hybrid # Combined analysis (default)
Usage
Basic Analysis
code2flow /path/to/project
Analysis Modes
# Static analysis only (fastest)
code2flow /path/to/project -m static
# Dynamic analysis with tracing
code2flow /path/to/project -m dynamic
# Hybrid analysis (recommended)
code2flow /path/to/project -m hybrid
# Behavioral pattern focus
code2flow /path/to/project -m behavioral
# Reverse engineering ready
code2flow /path/to/project -m reverse
Custom Output
code2flow /path/to/project -o my_analysis
Output Files
| File | Description |
|---|---|
analysis.yaml |
Complete structured analysis data |
analysis.json |
JSON format for programmatic use |
flow.mmd |
Full Mermaid flowchart (all nodes) |
compact_flow.mmd |
Compact flowchart - deduplicated nodes, grouped by function |
calls.mmd |
Function call graph |
cfg.png |
Control flow visualization |
call_graph.png |
Call graph visualization |
llm_prompt.md |
LLM-ready analysis summary |
Compact Flow Format
The compact_flow.mmd file provides optimized output:
- Deduplication: Identical node patterns are merged (e.g.,
x = 1,x = 2→x = N) - Function Subgraphs: Nodes grouped by function in subgraphs
- Pattern Preservation: Control flow structure maintained while reducing file size
- Import Reuse: Common patterns linked rather than duplicated
Example compact output:
flowchart TD
%% Function subgraphs
subgraph F12345["process_data"]
N1["x = N"]
N2{"if x > 0"}
N3[/"return x"/]
end
%% Edges reference deduplicated nodes
N1 --> N2
N2 -->|"true"| N3
Understanding the Output
LLM Prompt Structure
The generated prompt includes:
- System overview with metrics
- Call graph structure
- Behavioral patterns with confidence scores
- Data flow insights
- State machine definitions
- Reverse engineering guidelines
Behavioral Patterns
Each pattern includes:
- Name: Descriptive identifier
- Type: sequential, conditional, iterative, recursive, state_machine
- Entry/Exit points: Key functions
- Decision points: Conditional logic locations
- Data transformations: Variable dependencies
- Confidence: Pattern detection certainty
Reverse Engineering Guidelines
The analysis provides specific guidance for:
- Preserving call graph structure
- Implementing identified patterns
- Maintaining data dependencies
- Recreating state machines
- Preserving decision logic
Advanced Features
State Machine Detection
Automatically identifies:
- State variables
- Transition methods
- Source and destination states
- State machine hierarchy
Data Flow Tracking
Maps:
- Variable dependencies
- Data transformations
- Information flow paths
- Side effects
Dynamic Tracing
When using dynamic mode:
- Function entry/exit timing
- Call stack reconstruction
- Exception tracking
- Performance profiling
Integration with LLMs
The generated system_analysis_prompt.md is designed to be:
- Comprehensive: Contains all necessary system information
- Structured: Organized for easy parsing
- Actionable: Includes specific implementation guidance
- Language-agnostic: Describes behavior, not implementation
Example usage with an LLM:
"Based on the system analysis provided, implement this system in Go,
preserving all behavioral patterns and data flow characteristics."
Limitations
- Dynamic analysis requires test files
- Complex inheritance hierarchies may need manual review
- External library calls are treated as black boxes
- Runtime reflection and metaprogramming not fully captured
Contributing
The analyzer is designed to be extensible. Key areas for enhancement:
- Additional pattern types
- Language-specific optimizations
- Improved visualization
- Real-time analysis mode
License
Licensed under Apache-2.0.
Author
Tom Sapletta
Status
Last updated by taskill at 2026-04-25 13:36 UTC
| Metric | Value |
|---|---|
| HEAD | bdf9336 |
| Coverage | — |
| Failing tests | — |
| Commits in last cycle | 50 |
Large refactor and feature sweep: added a deep code analysis engine and supporting modules, improved configuration management and CLI, integrated AppDefaults for auto-loading a default LLM profile, and delegated env file I/O to getv.EnvStore. Docs, examples, and tests were updated alongside several chore/quality improvements and a release commit.
Metadata
Release files for code2logic 1.0.51
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| code2logic-1.0.51.tar.gz | 589.0 kB | Without provenance | Details for code2logic-1.0.51.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| code2logic-1.0.51-py3-none-any.whl | Python 3 | none | any | Details for code2logic-1.0.51-py3-none-any.whl |
Total release size: 927.7 kB
Release files / code2logic-1.0.51.tar.gz
| Download URL | code2logic-1.0.51.tar.gz |
|---|---|
| Size | 589.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
2393f4a89109a5ec6f9d190cf83c66d11d2f0e0c8faaa096b7f81a750569f516
|
|
BLAKE2b-256 checksum How to use checksums |
e6568a00d66b5eb901738514d1a7dd97fd20f8da30be591feac1e7a64d756856
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.13.7
|
Release files / code2logic-1.0.51-py3-none-any.whl
| Download URL | code2logic-1.0.51-py3-none-any.whl |
|---|---|
| Size | 338.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
2bcb15f359f9c24e9c43eaf5192a1088b717a5eae529711d2dfdf9e1d543cdda
|
|
BLAKE2b-256 checksum How to use checksums |
11ff9121457182ee73d288ef9ef3b8106361e997403d672a5fc42f246ddf8992
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.13.7
|
Security for code2logic 1.0.51
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.