High level conclusions

Fuzzers reach 52.48% code coverage.

Fuzzer fuzz_diff is blocked:

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

Fuzzer fuzz_repo is blocked:

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

Fuzzer fuzz_config is blocked:

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

Fuzzer fuzz_blob is blocked:

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

Fuzzer fuzz_submodule is blocked:

The runtime code coverage of fuzz_submodule covers 0.0% 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

55 / 663

Cyclomatic complexity statically reachable by fuzzers

231 / 2336

Runtime code coverage of functions

348 / 663

Warning: The number of runtime covered functions are larger than the number of reachable functions. This means that Fuzz Introspector found there are more functions covered at runtime than what is considered reachable based on the static analysis. This is a limitation in the analysis as anything covered at runtime is by definition reachable by the fuzzers.
This is likely due to a limitation in the static analysis. In this case, the count of functions covered at runtime is the true value, which means this is what should be considered "achieved" by the fuzzer.

Use the project functions table below to query all functions that were not covered at runtime.

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: fuzz_submodule

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

Call tree overview bitmap:

The distribution of callsites in terms of coloring is

Color	Runtime hitcount	Callsite count	Percentage
red	0	47	75.8%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	15	24.1%
All colors	62	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
44	17	...gitpython.fuzzing.fuzz-targets.fuzz_submodule.TestOneInput	call site: 00017	...gitpython.fuzzing.fuzz-targets.fuzz_submodule.sanitize_input
3	7	...gitpython.fuzzing.fuzz-targets.fuzz_submodule.TestOneInput	call site: 00007	...gitpython.fuzzing.fuzz-targets.fuzz_submodule.sanitize_input

Runtime coverage analysis

Covered functions

399

Functions that are reachable but not covered

33

Reachable functions

33

Percentage of reachable functions covered

0.0%

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.

Warning: The number of covered functions are larger than the number of reachable functions. This means that there are more functions covered at runtime than are extracted using static analysis. This is likely a result of the static analysis component failing to extract the right call graph or the coverage runtime being compiled with sanitizers in code that the static analysis has not analysed. This can happen if lto/gold is not used in all places that coverage instrumentation is used.

Function name	source code lines	source lines hit	percentage hit

Files reached

filename	functions hit
/	1
...gitpython.fuzzing.fuzz-targets.fuzz_submodule	32

Fuzzer: fuzz_blob

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

Call tree overview bitmap:

The distribution of callsites in terms of coloring is

Color	Runtime hitcount	Callsite count	Percentage
red	0	152	62.0%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	93	37.9%
All colors	245	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
75	5	git.util.expand_path	call site: 00005	typing.IO.tree.head.commit.resolve
34	96	git.util.is_cygwin_git	call site: 00096	git.util._is_cygwin_git
14	175	git.config.GitConfigParser.__init__	call site: 00175	git.config.get_config_path
6	147	git.repo.fun.is_git_dir	call site: 00147	os.path.join
6	217	git.repo.base.Repo.__init__	call site: 00217	git.repo.fun.find_worktree_git_dir
3	168	git.repo.base.Repo._get_config_path	call site: 00168	git.types.assert_never
2	156	git.repo.base.Repo.__init__	call site: 00156	git.repo.base.Repo._get_config_path
2	200	git.repo.base.Repo.__init__	call site: 00200	configparser.RawConfigParser.get
1	85	git.repo.base.Repo.init	call site: 00085	os.makedirs
1	92	git.repo.base.Repo.__init__	call site: 00092	os.getcwd
1	132	git.repo.base.Repo.__init__	call site: 00132	.str
1	134	git.repo.base.Repo.__init__	call site: 00134	warnings.warn

Runtime coverage analysis

Covered functions

400

Functions that are reachable but not covered

142

Reachable functions

165

Percentage of reachable functions covered

13.94%

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.

Warning: The number of covered functions are larger than the number of reachable functions. This means that there are more functions covered at runtime than are extracted using static analysis. This is likely a result of the static analysis component failing to extract the right call graph or the coverage runtime being compiled with sanitizers in code that the static analysis has not analysed. This can happen if lto/gold is not used in all places that coverage instrumentation is used.

Function name	source code lines	source lines hit	percentage hit

Files reached

filename	functions hit
/	1
...gitpython.fuzzing.fuzz-targets.fuzz_blob	9
git.repo.base	37
git.util	110
git.cmd	3
git.repo.fun	20
git.config	15
git.db	1

Fuzzer: fuzz_config

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

Call tree overview bitmap:

The distribution of callsites in terms of coloring is

Color	Runtime hitcount	Callsite count	Percentage
red	0	19	11.0%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	153	88.9%
All colors	172	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
13	144	git.config.GitConfigParser._included_paths	call site: 00144	git.config.GitConfigParser.items
4	162	git.config.GitConfigParser.read	call site: 00162	typing.cast
1	1	...gitpython.fuzzing.fuzz-targets.fuzz_config.TestOneInput	call site: 00001	git.config.GitConfigParser.read
1	170	git.config.GitConfigParser.read	call site: 00170	.str

Runtime coverage analysis

Covered functions

399

Functions that are reachable but not covered

146

Reachable functions

153

Percentage of reachable functions covered

4.58%

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.

Warning: The number of covered functions are larger than the number of reachable functions. This means that there are more functions covered at runtime than are extracted using static analysis. This is likely a result of the static analysis component failing to extract the right call graph or the coverage runtime being compiled with sanitizers in code that the static analysis has not analysed. This can happen if lto/gold is not used in all places that coverage instrumentation is used.

Function name	source code lines	source lines hit	percentage hit

Files reached

filename	functions hit
/	1
...gitpython.fuzzing.fuzz-targets.fuzz_config	3
git.config	150

Fuzzer: fuzz_repo

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

Call tree overview bitmap:

The distribution of callsites in terms of coloring is

Color	Runtime hitcount	Callsite count	Percentage
red	0	5	3.96%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	121	96.0%
All colors	126	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
4	52	...gitpython.fuzzing.fuzz-targets.fuzz_repo.TestOneInput	call site: 00052	os.path.join
1	0	EP	call site: 00000	atheris.FuzzedDataProvider

Runtime coverage analysis

Covered functions

400

Functions that are reachable but not covered

118

Reachable functions

122

Percentage of reachable functions covered

3.28%

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.

Warning: The number of covered functions are larger than the number of reachable functions. This means that there are more functions covered at runtime than are extracted using static analysis. This is likely a result of the static analysis component failing to extract the right call graph or the coverage runtime being compiled with sanitizers in code that the static analysis has not analysed. This can happen if lto/gold is not used in all places that coverage instrumentation is used.

Function name	source code lines	source lines hit	percentage hit

Files reached

filename	functions hit
/	1
...gitpython.fuzzing.fuzz-targets.fuzz_repo	64
git.objects.tree	2
git.objects.fun	4
git.compat	51

Fuzzer: fuzz_diff

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

Call tree overview bitmap:

The distribution of callsites in terms of coloring is

Color	Runtime hitcount	Callsite count	Percentage
red	0	1892	55.4%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	1521	44.5%
All colors	3413	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
895	1262	git.cmd.handle_process_output	call site: 01262	git.util.RemoteProgress.new_message_handler.handler
642	2770	git.util.finalize_process	call site: 02770	git.diff.Diff._handle_diff_line
299	954	git.cmd.handle_process_output	call site: 00954	...gitpython.fuzzing.fuzz-targets.fuzz_diff.BytesProcessAdapter.__init__
22	632	...gitpython.fuzzing.fuzz-targets.fuzz_diff.TestOneInput	call site: 00632	git.diff.Diff._index_from_patch_format
14	2458	git.util.RemoteProgress._parse_progress_line	call site: 02458	git.util.CallableRemoteProgress.update
7	613	git.objects.base.IndexObject.__init__	call site: 00613	git.objects.base.IndexObject.__init__
5	623	...gitpython.fuzzing.fuzz-targets.fuzz_diff.TestOneInput	call site: 00623	fdp.ConsumeBytes
3	607	git.diff.Diff.__init__	call site: 00607	a_rawpath.decode
2	1254	git.cmd.handle_process_output	call site: 01254	cmdline.split
1	299	...gitpython.fuzzing.fuzz-targets.fuzz_diff.TestOneInput	call site: 00299	git.diff.Diff.__init__
1	349	git.objects.util.mode_str_to_int	call site: 00349	io.BytesIO
1	2456	git.util.RemoteProgress._parse_progress_line	call site: 02456	line.decode

Runtime coverage analysis

Covered functions

400

Functions that are reachable but not covered

1848

Reachable functions

1861

Percentage of reachable functions covered

0.7%

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
...gitpython.fuzzing.fuzz-targets.fuzz_diff	608
git.diff	337
git.objects.util	301
git.objects.base	1
git.cmd	904
git.util	609

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
git.remote.Remote.push	git.remote	7	['N/A', 'N/A', 'N/A', 'N/A', 'N/A', 'N/A', 'N/A']	6	0	3	2	4	285	0	882	757

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

Functions statically reachable by fuzzers

72 / 663

Cyclomatic complexity statically reachable by fuzzers

293 / 2336

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

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/gitpython/fuzzing/fuzz-targets/fuzz_submodule.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=['...gitpython.fuzzing.fuzz-targets.fuzz_submodule.TestOneInput']

/src/gitpython/fuzzing/fuzz-targets/fuzz_blob.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=['git.util.expand_path', 'git.util.is_cygwin_git', 'git.config.GitConfigParser.__init__', 'git.repo.fun.is_git_dir', 'git.repo.base.Repo.__init__', 'git.repo.base.Repo._get_config_path', 'git.repo.base.Repo.init']

/src/gitpython/fuzzing/fuzz-targets/fuzz_config.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=['git.config.GitConfigParser._included_paths', 'git.config.GitConfigParser.read', '...gitpython.fuzzing.fuzz-targets.fuzz_config.TestOneInput']

/src/gitpython/fuzzing/fuzz-targets/fuzz_repo.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=['...gitpython.fuzzing.fuzz-targets.fuzz_repo.TestOneInput']

/src/gitpython/fuzzing/fuzz-targets/fuzz_diff.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=['git.cmd.handle_process_output', 'git.util.finalize_process', '...gitpython.fuzzing.fuzz-targets.fuzz_diff.TestOneInput', 'git.util.RemoteProgress._parse_progress_line', 'git.objects.base.IndexObject.__init__', 'git.diff.Diff.__init__']

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
s.encode	67	32	47.76%	['fuzz_submodule', 'fuzz_repo', 'fuzz_diff', 'fuzz_config', 'fuzz_blob']
repo.head.set_reference	39	17	43.58%	['fuzz_config', 'fuzz_submodule']
submodule.module_exists	64	33	51.56%	['fuzz_diff', 'fuzz_submodule']
git.refs.Head.create	39	20	51.28%	['fuzz_submodule']
git.cmd.handle_process_output.pump_stream	51	28	54.90%	['fuzz_submodule', 'fuzz_repo', 'fuzz_diff', 'fuzz_config', 'fuzz_blob']
git.cmd.Git.refresh	35	12	34.28%	['fuzz_submodule', 'fuzz_repo', 'fuzz_diff', 'fuzz_config', 'fuzz_blob']
git.cmd.Git.execute.communicate	34	16	47.05%	['fuzz_submodule', 'fuzz_repo', 'fuzz_diff', 'fuzz_config', 'fuzz_blob']
git.remote.PushInfo._from_line	32	0	0.0%	[]
git.util.RemoteProgress._parse_progress_line	44	12	27.27%	['fuzz_submodule', 'fuzz_repo', 'fuzz_diff', 'fuzz_config', 'fuzz_blob']
stream.read	300	141	47.0%	['fuzz_blob', 'fuzz_submodule', 'fuzz_repo']
git.objects.commit.Commit._deserialize	55	28	50.90%	['fuzz_submodule', 'fuzz_repo', 'fuzz_diff', 'fuzz_config', 'fuzz_blob']
git.repo.base.Repo.blame_incremental	39	0	0.0%	[]
git.repo.base.Repo.blame	75	0	0.0%	[]
git.objects.submodule.base.Submodule.add	56	30	53.57%	['fuzz_submodule', 'fuzz_repo', 'fuzz_diff', 'fuzz_config', 'fuzz_blob']
git.objects.submodule.base.Submodule.update	97	33	34.02%	['fuzz_submodule', 'fuzz_repo', 'fuzz_diff', 'fuzz_config', 'fuzz_blob']
git.objects.submodule.base.Submodule.move	49	0	0.0%	[]
git.objects.submodule.base.Submodule.remove	60	0	0.0%	[]
git.objects.util.parse_date	46	2	4.347%	['fuzz_submodule', 'fuzz_repo', 'fuzz_diff', 'fuzz_config', 'fuzz_blob']
ref.set_reference	45	10	22.22%	['fuzz_submodule', 'fuzz_repo', 'fuzz_diff', 'fuzz_config', 'fuzz_blob']
git.objects.submodule.root.RootModule.update	104	0	0.0%	[]
git.repo.fun.rev_parse	100	22	22.0%	['fuzz_submodule', 'fuzz_repo', 'fuzz_diff', 'fuzz_config', 'fuzz_blob']
git.index.base.IndexFile.checkout.handle_stderr	49	0	0.0%	[]
f.readline	56	20	35.71%	['fuzz_submodule', 'fuzz_repo', 'fuzz_diff', 'fuzz_config', 'fuzz_blob']
git.index.fun.aggressive_tree_merge	36	0	0.0%	[]
git.diff.Diffable.diff	39	5	12.82%	['fuzz_submodule', 'fuzz_repo', 'fuzz_diff', 'fuzz_config', 'fuzz_blob']
git.diff.Diff.__str__	33	0	0.0%	['fuzz_diff']
git.diff.Diff._handle_diff_line	39	0	0.0%	['fuzz_diff']
buf.find	70	16	22.85%	['fuzz_submodule', 'fuzz_repo', 'fuzz_diff', 'fuzz_config', 'fuzz_blob']

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
	[]	[]
threading	[]	[]
git.refs	[]	[]
git.objects.submodule	[]	[]
git.index.util	[]	[]
textwrap	[]	[]
locale	[]	[]
pathlib	[]	[]
io	[]	[]
git.objects.util	['fuzz_diff']	[]
warnings	[]	[]
git.util	['fuzz_blob', 'fuzz_diff']	[]
git.objects.fun	['fuzz_repo']	[]
typing	[]	[]
subprocess	[]	[]
mimetypes	[]	[]
git.objects.base	['fuzz_diff']	[]
git.remote	[]	[]
gitdb	[]	[]
inspect	[]	[]
git.index.fun	[]	[]
git.objects.submodule.base	[]	[]
getpass	[]	[]
git.objects.submodule.util	[]	[]
shutil	[]	[]
git.repo	[]	[]
tempfile	[]	[]
...gitpython.fuzzing.fuzz-targets.fuzz_diff	['fuzz_diff']	[]
git.exc	[]	[]
git.refs.reference	[]	[]
git.config	['fuzz_blob', 'fuzz_config']	[]
git.refs.remote	[]	[]
git.db	['fuzz_blob']	[]
git.index.base	[]	[]
shlex	[]	[]
git.objects	[]	[]
git.repo.fun	['fuzz_blob']	[]
functools	[]	[]
atheris	[]	[]
git.refs.log	[]	[]
sys	[]	[]
urllib	[]	[]
utils	[]	[]
...gitpython.fuzzing.fuzz-targets.fuzz_submodule	['fuzz_submodule']	[]
gc	[]	[]
git.objects.tree	['fuzz_repo']	[]
stat	[]	[]
git.refs.head	[]	[]
enum	[]	[]
os	[]	[]
configparser	[]	[]
git.repo.base	['fuzz_blob']	[]
git.index.typ	[]	[]
git	[]	[]
git.diff	['fuzz_diff']	[]
git.refs.tag	[]	[]
platform	[]	[]
git.objects.commit	[]	[]
typing_extensions	[]	[]
binascii	[]	[]
weakref	[]	[]
importlib	[]	[]
struct	[]	[]
...gitpython.fuzzing.fuzz-targets.fuzz_config	['fuzz_config']	[]
collections	[]	[]
git.objects.blob	[]	[]
git.cmd	['fuzz_blob', 'fuzz_diff']	[]
...gitpython.fuzzing.fuzz-targets.fuzz_blob	['fuzz_blob']	[]
	[]	[]
git.refs.symbolic	[]	[]
itertools	[]	[]
uuid	[]	[]
git.objects.tag	[]	[]
git.types	[]	[]
fnmatch	[]	[]
...gitpython.fuzzing.fuzz-targets.fuzz_repo	['fuzz_repo']	[]
time	[]	[]
logging	[]	[]
calendar	[]	[]
git.objects.submodule.root	[]	[]
glob	[]	[]
datetime	[]	[]
contextlib	[]	[]
git.index	[]	[]
re	[]	[]
git.compat	['fuzz_repo']	[]

Directories in report

Directory