High level conclusions

Fuzzers reach 51.74% code coverage.

Fuzzer fuzz_repo is blocked:

The runtime code coverage of fuzz_repo covers 6.535% 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 5.405% 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_diff is blocked:

The runtime code coverage of fuzz_diff covers 14.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_blob is blocked:

The runtime code coverage of fuzz_blob covers 25.27% 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 20.35% 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

62 / 659

Cyclomatic complexity statically reachable by fuzzers

267 / 2325

Runtime code coverage of functions

341 / 659

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	122	56.4%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	94	43.5%
All colors	216	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
33	22	git.util.is_cygwin_git	call site: 00022	git.util._is_cygwin_git
26	189	...gitpython.fuzzing.fuzz-targets.fuzz_submodule.TestOneInput	call site: 00189	...gitpython.fuzzing.fuzz-targets.fuzz_submodule.sanitize_input
14	95	git.config.GitConfigParser.__init__	call site: 00095	git.config.get_config_path
12	176	...gitpython.fuzzing.fuzz-targets.fuzz_submodule.TestOneInput	call site: 00176	...gitpython.fuzzing.fuzz-targets.fuzz_submodule.sanitize_input
10	156	git.db.GitCmdObjectDB.__init__	call site: 00156	git.repo.base.Repo.init
6	69	git.repo.fun.is_git_dir	call site: 00069	os.path.join
6	137	git.repo.base.Repo.__init__	call site: 00137	git.repo.fun.find_worktree_git_dir
3	0	EP	call site: 00000	git.repo.base.Repo.init
2	89	git.repo.base.Repo._get_config_path	call site: 00089	git.types.assert_never
2	120	git.repo.base.Repo.__init__	call site: 00120	configparser.RawConfigParser.get
1	10	git.repo.base.Repo.init	call site: 00010	os.makedirs
1	17	git.repo.base.Repo.__init__	call site: 00017	os.getcwd

Runtime coverage analysis

Covered functions

398

Functions that are reachable but not covered

90

Reachable functions

113

Percentage of reachable functions covered

20.35%

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
git.repo.base	35
git.util	36
git.cmd	3
git.repo.fun	20
git.config	15
git.db	1

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	82	49.6%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	83	50.3%
All colors	165	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
33	22	git.util.is_cygwin_git	call site: 00022	git.util._is_cygwin_git
14	95	git.config.GitConfigParser.__init__	call site: 00095	git.config.get_config_path
8	156	git.db.GitCmdObjectDB.__init__	call site: 00156	git.db.GitCmdObjectDB.__init__
6	69	git.repo.fun.is_git_dir	call site: 00069	os.path.join
6	137	git.repo.base.Repo.__init__	call site: 00137	git.repo.fun.find_worktree_git_dir
3	0	EP	call site: 00000	git.repo.base.Repo.init
2	89	git.repo.base.Repo._get_config_path	call site: 00089	git.types.assert_never
2	120	git.repo.base.Repo.__init__	call site: 00120	configparser.RawConfigParser.get
1	10	git.repo.base.Repo.init	call site: 00010	os.makedirs
1	17	git.repo.base.Repo.__init__	call site: 00017	os.getcwd
1	56	git.repo.base.Repo.__init__	call site: 00056	warnings.warn
1	64	git.repo.fun.is_git_dir	call site: 00064	os.path.join

Runtime coverage analysis

Covered functions

398

Functions that are reachable but not covered

68

Reachable functions

91

Percentage of reachable functions covered

25.27%

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	35
git.util	36
git.cmd	3
git.repo.fun	20
git.config	15
git.db	1

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	195	53.4%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	170	46.5%
All colors	365	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
50	314	git.util.finalize_process	call site: 00314	git.diff.Diff._handle_diff_line
37	227	git.cmd.handle_process_output	call site: 00227	git.util.RemoteProgress.new_message_handler.handler
33	22	git.util.is_cygwin_git	call site: 00022	git.util._is_cygwin_git
14	95	git.config.GitConfigParser.__init__	call site: 00095	git.config.get_config_path
12	300	git.util.RemoteProgress._parse_progress_line	call site: 00300	git.util.CallableRemoteProgress.update
6	69	git.repo.fun.is_git_dir	call site: 00069	os.path.join
6	137	git.repo.base.Repo.__init__	call site: 00137	git.repo.fun.find_worktree_git_dir
6	207	...gitpython.fuzzing.fuzz-targets.fuzz_diff.TestOneInput	call site: 00207	git.diff.Diff._index_from_patch_format
4	172	git.objects.base.IndexObject.__init__	call site: 00172	git.objects.base.IndexObject.__init__
4	183	...gitpython.fuzzing.fuzz-targets.fuzz_diff.TestOneInput	call site: 00183	fdp.ConsumeBytes
3	166	git.diff.Diff.__init__	call site: 00166	a_rawpath.decode
2	89	git.repo.base.Repo._get_config_path	call site: 00089	git.types.assert_never

Runtime coverage analysis

Covered functions

398

Functions that are reachable but not covered

188

Reachable functions

221

Percentage of reachable functions covered

14.93%

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_diff	15
git.repo.base	35
git.util	80
git.cmd	49
git.repo.fun	20
git.config	15
git.db	1
git.diff	40
git.objects.util	4
git.objects.base	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.3%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	148	88.6%
All colors	167	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
15	137	git.config.GitConfigParser._included_paths	call site: 00137	git.config.GitConfigParser.items
4	157	git.config.GitConfigParser.read	call site: 00157	typing.cast

Runtime coverage analysis

Covered functions

399

Functions that are reachable but not covered

140

Reachable functions

148

Percentage of reachable functions covered

5.41%

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	144

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	360	53.6%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	311	46.3%
All colors	671	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
117	541	git.repo.base.Repo.__init__	call site: 00541	git.repo.base.Repo.tree
103	265	git.repo.fun.name_to_object	call site: 00265	git.repo.fun.short_to_long
52	380	git.repo.fun.rev_parse	call site: 00380	git.repo.base.Repo.__init__
33	22	git.util.is_cygwin_git	call site: 00022	git.util._is_cygwin_git
14	95	git.config.GitConfigParser.__init__	call site: 00095	git.repo.base.Repo.__init__
6	69	git.repo.fun.is_git_dir	call site: 00069	os.path.join
6	137	git.repo.base.Repo.__init__	call site: 00137	git.repo.fun.find_worktree_git_dir
6	465	git.repo.base.Repo.__init__	call site: 00465	datetime.timedelta._get_object
4	371	git.repo.fun.name_to_object	call site: 00371	git.repo.base.Repo.__init__
3	0	EP	call site: 00000	git.repo.base.Repo.init
2	89	git.repo.base.Repo._get_config_path	call site: 00089	git.types.assert_never
2	120	git.repo.base.Repo.__init__	call site: 00120	configparser.RawConfigParser.get

Runtime coverage analysis

Covered functions

398

Functions that are reachable but not covered

429

Reachable functions

459

Percentage of reachable functions covered

6.54%

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_repo	15
git.repo.base	139
git.util	36
git.cmd	3
git.repo.fun	275
git.config	15
git.refs.symbolic	6
git.db	1
git.objects.tree	2
git.objects.fun	4
git.compat	2

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.objects.submodule.base.Submodule.update	git.objects.submodule.base	12	['N/A', 'N/A', 'N/A', 'N/A', 'N/A', 'N/A', 'N/A', 'N/A', 'N/A', 'N/A', 'N/A', 'N/A']	9	0	22	26	13	474	1	1505	584
git.objects.submodule.root.RootModule.update	git.objects.submodule.root	10	['N/A', 'N/A', 'N/A', 'N/A', 'N/A', 'N/A', 'N/A', 'N/A', 'N/A', 'N/A']	9	0	20	24	13	363	0	1143	479
git.refs.symbolic.SymbolicReference._get_ref_info_helper	git.refs.symbolic	3	['N/A', 'N/A', 'N/A']	1	0	2	5	5	63	0	194	182

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

Functions statically reachable by fuzzers

110 / 659

Cyclomatic complexity statically reachable by fuzzers

467 / 2325

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=['git.util.is_cygwin_git', '...gitpython.fuzzing.fuzz-targets.fuzz_submodule.TestOneInput', 'git.config.GitConfigParser.__init__', 'git.db.GitCmdObjectDB.__init__', 'git.repo.fun.is_git_dir', 'git.repo.base.Repo.__init__', 'git.repo.base.Repo._get_config_path']

/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.is_cygwin_git', 'git.config.GitConfigParser.__init__', 'git.db.GitCmdObjectDB.__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_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.util.finalize_process', 'git.cmd.handle_process_output', 'git.util.is_cygwin_git', 'git.config.GitConfigParser.__init__', 'git.util.RemoteProgress._parse_progress_line', 'git.repo.fun.is_git_dir', 'git.repo.base.Repo.__init__', '...gitpython.fuzzing.fuzz-targets.fuzz_diff.TestOneInput', 'git.objects.base.IndexObject.__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']

/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=['git.repo.base.Repo.__init__', 'git.repo.fun.name_to_object', 'git.repo.fun.rev_parse', 'git.util.is_cygwin_git', 'git.config.GitConfigParser.__init__', 'git.repo.fun.is_git_dir']

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

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

Directories in report

Directory