Fuzz introspector
For issues and ideas: https://github.com/ossf/fuzz-introspector/issues
Project coverage

Table of contents

Project overview: tqdm
High level conclusions
Reachability and coverage overview
Fuzzers overview
Project functions overview
Fuzzer details
Fuzzer: fuzz_tqdm
Call tree
Fuzz blockers
Runtime coverage analysis
Files reached
Analyses and suggestions
Optimal target analysis
Remaining optimal interesting functions
All functions overview
Runtime coverage analysis
Complex functions with low coverage
Files and Directories in report
Files in report
Directories in report
Metadata section
Function call coverage
Function in each files in report
Report generation date: 2023-06-07

Project overview: tqdm

High level conclusions

Reachability and coverage overview

Functions statically reachable by fuzzers
24.0%
50 / 212
Cyclomatic complexity statically reachable by fuzzers
26.0%
192 / 739
Runtime code coverage of functions
1.0%
2 / 212

Fuzzers overview

Fuzzer Fuzzer filename Functions Reached Functions unreached Fuzzer depth Files reached Basic blocks reached Cyclomatic complexity Details
fuzz_tqdm /src/fuzz_tqdm.py 154 369 11 12 117 502 fuzz_tqdm.py

Project functions overview

The following table shows data about each function in the project. The functions included in this table correspond to all functions that exist in the executables of the fuzzers. As such, there may be functions that are from third-party libraries.

For further technical details on the meaning of columns in the below table, please see the Glossary .

Func name Functions filename Args Function call depth Reached by Fuzzers Fuzzers runtime hit Func lines hit % I Count BB Count Cyclomatic complexity Functions reached Reached by functions Accumulated cyclomatic complexity Undiscovered complexity

Fuzzer details

Fuzzer: fuzz_tqdm

Call tree

The calltree shows the control flow of the fuzzer. This is overlaid with coverage information to display how much of the potential code a fuzzer can reach is in fact covered at runtime. In the following there is a link to a detailed calltree visualisation as well as a bitmap showing a high-level view of the calltree. For further information about these topics please see the glossary for full calltree and calltree overview

Full calltree

Call tree overview bitmap:

The distribution of callsites in terms of coloring is
Color Runtime hitcount Callsite count Percentage
red 0 251 87.7%
gold [1:9] 0 0.0%
yellow [10:29] 0 0.0%
greenyellow [30:49] 0 0.0%
lawngreen 50+ 35 12.2%
All colors 286 100

Fuzz blockers

The following nodes represent call sites where fuzz blockers occur.

Amount of callsites blocked Calltree index Parent function Callsite Largest blocked function
138 19 ...fuzz_tqdm.TestOneInput call site: 00019 tqdm.std.tqdm.set_postfix
49 191 tqdm.contrib.discord.DiscordIO.write call site: 00191 tqdm.contrib.slack.tqdm_slack.display
27 257 tqdm.contrib.telegram.TelegramIO.write call site: 00257 tqdm.std.tqdm.refresh
19 169 tqdm.contrib.utils_worker.MonoWorker.submit call site: 00169 tqdm.std.tqdm.external_write_mode
12 244 tqdm.contrib.slack.SlackIO.write call site: 00244 tqdm.contrib.telegram.tqdm_telegram.display
4 13 ...fuzz_tqdm.gen_random_list call site: 00013 fdp.ConsumeUnicode
1 163 tqdm.contrib.utils_worker.MonoWorker.submit call site: 00163 collections.deque.pop
1 165 tqdm.contrib.utils_worker.MonoWorker.submit call site: 00165 collections.deque.appendleft

Runtime coverage analysis

Covered functions
3
Functions that are reachable but not covered
153
Reachable functions
154
Percentage of reachable functions covered
0.65%
NB: The sum of covered functions and functions that are reachable but not covered need not be equal to Reachable functions . This is because the reachability analysis is an approximation and thus at runtime some functions may be covered that are not included in the reachability analysis. This is a limitation of our static analysis capabilities.
Function name source code lines source lines hit percentage hit

Files reached

filename functions hit
/ 1
...fuzz_tqdm 12
tqdm.std 82
tqdm.utils 34
tqdm.rich 2
tqdm.tk 2
tqdm.contrib.discord 7
tqdm.contrib.utils_worker 10
tqdm.gui 14
tqdm.contrib.slack 7
tqdm.notebook 17
tqdm.contrib.telegram 7

Analyses and suggestions

Optimal target analysis

Remaining optimal interesting functions

The following table shows a list of functions that are optimal targets. Optimal targets are identified by finding the functions that in combination, yield a high code coverage.

Func name Functions filename Arg count Args Function depth hitcount instr count bb count cyclomatic complexity Reachable functions Incoming references total cyclomatic complexity Unreached complexity
tqdm.cli.main tqdm.cli 2 ['N/A', 'N/A'] 4 0 28 17 10 205 1 683 209
tqdm.gui.tqdm_gui.__init__ tqdm.gui 3 ['N/A', 'N/A', 'N/A'] 1 0 15 4 5 24 1 77 53
tqdm.tk.tqdm_tk.__init__ tqdm.tk 3 ['N/A', 'N/A', 'N/A'] 1 0 14 6 5 19 1 62 47
tqdm.keras.TqdmCallback.on_epoch_begin tqdm.keras 4 ['N/A', 'N/A', 'N/A', 'N/A'] 4 0 2 5 5 131 0 437 39

Implementing fuzzers that target the above functions will improve reachability such that it becomes:

Functions statically reachable by fuzzers
38.0%
80 / 212
Cyclomatic complexity statically reachable by fuzzers
43.0%
315 / 739

All functions overview

If you implement fuzzers for these functions, the status of all functions in the project will be:

Func name Functions filename Args Function call depth Reached by Fuzzers Fuzzers runtime hit Func lines hit % I Count BB Count Cyclomatic complexity Functions reached Reached by functions Accumulated cyclomatic complexity Undiscovered complexity

Runtime coverage analysis

This section shows analysis of runtime coverage data.

For futher technical details on how this section is generated, please see the Glossary .

Complex functions with low coverage

Func name Function total lines Lines covered at runtime percentage covered Reached by fuzzers

Files and Directories in report

This section shows which files and directories are considered in this report. The main reason for showing this is fuzz introspector may include more code in the reasoning than is desired. This section helps identify if too many files/directories are included, e.g. third party code, which may be irrelevant for the threat model. In the event too much is included, fuzz introspector supports a configuration file that can exclude data from the report. See the following link for more information on how to create a config file: link

Files in report

Source file Reached by Covered by
[] []
tqdm.contrib.logging [] []
tqdm.version [] []
tqdm.contrib.concurrent [] []
shlex [] []
tqdm._monitor [] []
tqdm.notebook ['fuzz_tqdm'] []
subprocess [] []
tqdm.contrib.itertools [] []
[] []
shutil [] []
operator [] []
html [] []
threading [] []
tqdm.contrib.telegram ['fuzz_tqdm'] []
requests [] []
tqdm.autonotebook [] []
tqdm.contrib.discord ['fuzz_tqdm'] []
tqdm.__main__ [] []
cgi [] []
time [] []
copy [] []
weakref [] []
warnings [] []
tqdm.dask [] []
numpy [] []
...fuzz_tqdm ['fuzz_tqdm'] []
tqdm [] []
tqdm.gui ['fuzz_tqdm'] []
concurrent [] []
atheris [] []
ipywidgets [] []
tqdm.contrib [] []
pandas [] []
ctypes [] []
tqdm._main [] []
logging [] []
setuptools_scm [] []
colorama [] []
tqdm.utils ['fuzz_tqdm'] []
rich [] []
tqdm.contrib.utils_worker ['fuzz_tqdm'] []
atexit [] []
tqdm.rich ['fuzz_tqdm'] []
matplotlib [] []
collections [] []
fcntl [] []
re [] []
tensorflow [] []
tqdm.tk ['fuzz_tqdm'] []
importlib [] []
tqdm._utils [] []
tqdm.contrib.bells [] []
struct [] []
slack_sdk [] []
tqdm._dist_ver [] []
tqdm.contrib.slack ['fuzz_tqdm'] []
tqdm._tqdm [] []
itertools [] []
datetime [] []
disco [] []
tqdm.cli [] []
tqdm._tqdm_notebook [] []
functools [] []
asyncio [] []
sys [] []
unicodedata [] []
tqdm._tqdm_gui [] []
multiprocessing [] []
ast [] []
tqdm.std ['fuzz_tqdm'] []
tqdm.auto [] []
tqdm._tqdm_pandas [] []
os [] []
array [] []
tqdm.asyncio [] []
tkinter [] []
tqdm.keras [] []
IPython [] []

Directories in report

Directory

Metadata section

This sections shows the raw data that is used to produce this report. This is mainly used for further processing and developer debugging.

Fuzzer Calltree file Program data file Coverage file
fuzz_tqdm fuzzerLogFile-fuzz_tqdm.data fuzzerLogFile-fuzz_tqdm.data.yaml all_cov.json