Report generation date: 2025-11-24

Project overview: tqdm

High level conclusions

The runtime code coverage of fuzz_tqdm covers 1.307% of its statically reachable code. This means there is some place that blocks the fuzzer to continue exploring more code at run time.

Reachability and coverage overview

Functions statically reachable by fuzzers

49 / 217

Cyclomatic complexity statically reachable by fuzzers

189 / 759

Runtime code coverage of functions

3 / 217

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	153	384	11	12	115	499	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	Runtime reached by Fuzzers	Combined 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 250 88.6%

gold [1:9] 0 0.0%

yellow [10:29] 0 0.0%

greenyellow [30:49] 0 0.0%

lawngreen 50+ 32 11.3%

All colors 282 100

Color	Runtime hitcount	Callsite count	Percentage
red	0	250	88.6%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	32	11.3%
All colors	282	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
181	19	...fuzz_tqdm.TestOneInput	call site: 00019	tqdm.std.tqdm.set_postfix
23	257	tqdm.contrib.discord.DiscordIO.write	call site: 00257	tqdm.std.tqdm.refresh
19	212	tqdm.contrib.utils_worker.MonoWorker.submit	call site: 00212	tqdm.std.tqdm.external_write_mode
13	234	tqdm.contrib.slack.SlackIO.write	call site: 00234	tqdm.contrib.telegram.tqdm_telegram.display
8	248	tqdm.contrib.telegram.TelegramIO.write	call site: 00248	tqdm.contrib.discord.tqdm_discord.display
4	13	...fuzz_tqdm.gen_random_list	call site: 00013	fdp.ConsumeUnicode
1	206	tqdm.contrib.utils_worker.MonoWorker.submit	call site: 00206	collections.deque.pop
1	208	tqdm.contrib.utils_worker.MonoWorker.submit	call site: 00208	collections.deque.appendleft

Runtime coverage analysis

Covered functions

4

Functions that are reachable but not covered

151

Reachable functions

153

Percentage of reachable functions covered

1.31%

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	80
tqdm.utils	34
tqdm.gui	16
tqdm.tk	2
tqdm.contrib.slack	7
tqdm.contrib.utils_worker	10
tqdm.notebook	16
tqdm.contrib.telegram	7
tqdm.contrib.discord	7
tqdm.rich	2

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	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']	5	28	17	10	202	1	671	203
`tqdm.gui.tqdm_gui.__init__`	tqdm.gui	3	['N/A', 'N/A', 'N/A']	2	15	4	5	24	1	77	56
`tqdm.tk.tqdm_tk.__init__`	tqdm.tk	3	['N/A', 'N/A', 'N/A']	2	14	6	5	19	1	62	47
`tqdm.keras.TqdmCallback.on_epoch_begin`	tqdm.keras	4	['N/A', 'N/A', 'N/A', 'N/A']	8	2	5	5	130	0	432	39

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

Functions statically reachable by fuzzers

77 / 217

Cyclomatic complexity statically reachable by fuzzers

303 / 759

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	Runtime reached by Fuzzers	Combined 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

Fuzz engine guidance

This sections provides heuristics that can be used as input to a fuzz engine when running a given fuzz target. The current focus is on providing input that is usable by libFuzzer.

/src/fuzz_tqdm.py

Dictionary

Use this with the libFuzzer -dict=DICT.file flag

Fuzzer function priority

Use one of these functions as input to libfuzzer with flag: -focus_function name

-focus_function=['...fuzz_tqdm.TestOneInput', 'tqdm.contrib.discord.DiscordIO.write', 'tqdm.contrib.utils_worker.MonoWorker.submit', 'tqdm.contrib.slack.SlackIO.write', 'tqdm.contrib.telegram.TelegramIO.write', '...fuzz_tqdm.gen_random_list']

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.asyncio	[]	[]
subprocess	[]	[]
warnings	[]	[]
tensorflow	[]	[]
tqdm.contrib	[]	[]
tqdm.contrib.telegram	['fuzz_tqdm']	[]
asyncio	[]	[]
operator	[]	[]
tqdm.contrib.discord	['fuzz_tqdm']	[]
importlib	[]	[]
atheris	[]	[]
tqdm.cli	[]	[]
tqdm._tqdm_notebook	[]	[]
tqdm.notebook	['fuzz_tqdm']	[]
slack_sdk	[]	[]
itertools	[]	[]
inspect	[]	[]
html	[]	[]
numpy	[]	[]
tqdm._utils	[]	[]
tqdm._tqdm_gui	[]	[]
weakref	[]	[]
tqdm.contrib.itertools	[]	[]
matplotlib	[]	[]
tqdm.utils	['fuzz_tqdm']	[]
tqdm._monitor	[]	[]
pandas	[]	[]
requests	[]	[]
tqdm.__main__	[]	[]
struct	[]	[]
tqdm._tqdm_pandas	[]	[]
tqdm.contrib.bells	[]	[]
rich	[]	[]
atexit	[]	[]
tqdm._main	[]	[]
array	[]	[]
pathlib	[]	[]
tqdm.contrib.utils_worker	['fuzz_tqdm']	[]
tqdm.rich	['fuzz_tqdm']	[]
re	[]	[]
ipywidgets	[]	[]
functools	[]	[]
tqdm.gui	['fuzz_tqdm']	[]
tqdm.keras	[]	[]
tqdm._tqdm	[]	[]
IPython	[]	[]
datetime	[]	[]
tqdm.std	['fuzz_tqdm']	[]
tqdm._dist_ver	[]	[]
...fuzz_tqdm	['fuzz_tqdm']	[]
tqdm.dask	[]	[]
tqdm.tk	['fuzz_tqdm']	[]
textwrap	[]	[]
fcntl	[]	[]
concurrent	[]	[]
unicodedata	[]	[]
time	[]	[]
tqdm.autonotebook	[]	[]
logging	[]	[]
ctypes	[]	[]
	[]	[]
threading	[]	[]
tqdm.contrib.concurrent	[]	[]
sys	[]	[]
shlex	[]	[]
tqdm.auto	[]	[]
tqdm	[]	[]
tkinter	[]	[]
tqdm.contrib.logging	[]	[]
os	[]	[]
ast	[]	[]
multiprocessing	[]	[]
copy	[]	[]
importlib_resources	[]	[]
setuptools_scm	[]	[]
tqdm.contrib.slack	['fuzz_tqdm']	[]
tqdm.version	[]	[]
colorama	[]	[]
collections	[]	[]

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

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

Fuzz engine guidance

/src/fuzz_tqdm.py

Dictionary

Fuzzer function priority

Runtime coverage analysis

Complex functions with low coverage

Files and Directories in report

Files in report

Directories in report

Metadata section