code2flowdiagram

code2flowdiagram generates call graphs for dynamic programming language. code2flowdiagram supports Python, JavaScript, Ruby, and PHP.

The basic algorithm is simple:

1. Translate your source files into ASTs.
2. Find all function definitions.
3. Determine where those functions are called.
4. Connect the dots.

code2flowdiagram is useful for:

• Untangling spaghetti code.
• Identifying orphaned functions.
• Getting new developers up to speed.

code2flowdiagram provides a pretty good estimate of your project's structure. No algorithm can generate a perfect call graph for a dynamic language – even less so if that language is duck-typed. See the known limitations in the section below.

(Below: code2flowdiagram running against a subset of itself code2flowdiagram code2flowdiagram/engine.py code2flowdiagram/python.py --target-function=code2flowdiagram --downstream-depth=3)

Installation

pip3 install code2flowdiagram

If you don't have it already, you will also need to install graphviz. Installation instructions can be found here.

Additionally, depending on the language you want to parse, you may need to install additional dependencies:

• JavaScript: Acorn
• Ruby: Parser
• PHP: PHP-Parser
• Python: No extra dependencies needed

Usage

To generate a DOT file, run something like:

code2flowdiagram mypythonfile.py

Or, for Javascript:

code2flowdiagram myjavascriptfile.js

You can specify multiple files or import directories:

code2flowdiagram project/directory/source_a.js project/directory/source_b.js

code2flowdiagram project/directory/*.js

code2flowdiagram project/directory --language js

To pull out a subset of the graph, try something like:

code2flowdiagram mypythonfile.py --target-function my_func --upstream-depth=1 --downstream-depth=1

There are a ton of command line options, to see them all, run:

code2flowdiagram --help

How code2flowdiagram works

code2flowdiagram approximates the structure of projects in dynamic languages. It is not possible to generate a perfect callgraph for a dynamic language.

Detailed algorithm:

1. Generate an AST of the source code
2. Recursively separate groups and nodes. Groups are files, modules, or classes. More precisely, groups are namespaces where functions live. Nodes are the functions themselves.
3. For all nodes, identify function calls in those nodes.
4. For all nodes, identify in-scope variables. Attempt to connect those variables to specific nodes and groups. This is where there is some ambiguity in the algorithm because it is impossible to know the types of variables in dynamic languages. So, instead, heuristics must be used.
5. For all calls in all nodes, attempt to find a match from the in-scope variables. This will be an edge.
6. If a definitive match from in-scope variables cannot be found, attempt to find a single match from all other groups and nodes.
7. Trim orphaned nodes and groups.
8. Output results.

Why is it impossible to generate a perfect call graph?

Consider this toy example in Python

def func_factory(param):
    if param < .5:
        return func_a
    else:
        return func_b

func = func_factory(important_variable)
func()

We have no way of knowing whether func will point to func_a or func_b until runtime. In practice, ambiguity like this is common and is present in most non-trivial applications.

Known limitations

code2flowdiagram is internally powered by ASTs. Most limitations stem from a token not being named what code2flowdiagram expects it to be named.

• All functions without definitions are skipped. This most often happens when a file is not included.
• Functions with identical names in different namespaces are (loudly) skipped. E.g. If you have two classes with identically named methods, code2flowdiagram cannot distinguish between these and skips them.
• Imported functions from outside your project directory (including from standard libraries) which share names with your defined functions may not be handled correctly. Instead, when you call the imported function, code2flowdiagram will link to your local functions. For example, if you have a function search() and call, import searcher; searcher.search(), code2flowdiagram may link (incorrectly) to your defined function.
• Anonymous or generated functions are skipped. This includes lambdas and factories.
• If a function is renamed, either explicitly or by being passed around as a parameter, it will be skipped.

As an imported library

You can work with code2flowdiagram as an imported Python library in much the same way as you work with it from the CLI.

import code2flowdiagram
code2flowdiagram.code2flowdiagram(['path/to/filea', 'path/to/fileb'], 'path/to/outputfile')

The keyword arguments to code2flowdiagram.code2flowdiagram are roughly the same as the CLI parameters. To see all available parameters, refer to the code2flowdiagram function in engine.py.

How to contribute

1. Open an issue: code2flowdiagram is not perfect and there is a lot that can be improved. If you find a problem parsing your source that you can identify with a simplified example, please open an issue.
2. Create a PR: Even better, if you have a fix for the issue you identified that passes unit tests, please open a PR.
3. Add a language: While dense, each language implementation is between 250-400 lines of code including comments. If you want to implement another language, the existing implementations can be your guide.

Unit tests

Test coverage is 100%. To run:

    pip install -r requirements_dev.txt
    make test

License

code2flowdiagram is licensed under the MIT license. Prior to the rewrite in April 2021, code2flowdiagram was licensed under LGPL. The last commit under that license was 24b2cb854c6a872ba6e17409fbddb6659bf64d4c. The April 2021 rewrite was substantial, so it's probably reasonable to treat code2flowdiagram as completely MIT-licensed.

Feedback / Issues / Contact

If you have an issue using code2flowdiagram or a feature request, please post it in the issues tab.