High level conclusions

Fuzzers reach 55.97% code coverage.

Fuzzer fuzz_repo is blocked:

The runtime code coverage of fuzz_repo covers 1.769% 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.635% 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 13.06% 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 16.66% 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 17.85% 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

53 / 661

Cyclomatic complexity statically reachable by fuzzers

226 / 2331

Runtime code coverage of functions

370 / 661

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_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	200	57.8%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	146	42.1%
All colors	346	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
34	22	git.util.is_cygwin_git	call site: 00022	git.util._is_cygwin_git
25	295	git.util.finalize_process	call site: 00295	git.diff.Diff.__init__
24	321	...gitpython.fuzzing.fuzz-targets.fuzz_diff.BytesProcessAdapter.__init__	call site: 00321	git.diff.Diff._handle_diff_line
22	199	...gitpython.fuzzing.fuzz-targets.fuzz_diff.TestOneInput	call site: 00199	git.diff.Diff._index_from_patch_format
18	235	git.cmd.handle_process_output	call site: 00235	git.util.RemoteProgress.new_message_handler.handler
14	101	git.config.GitConfigParser.__init__	call site: 00101	git.config.get_config_path
11	270	git.util.RemoteProgress._parse_progress_line	call site: 00270	git.util.finalize_process
8	179	git.objects.base.IndexObject.__init__	call site: 00179	git.objects.base.IndexObject.__init__
6	73	git.repo.fun.is_git_dir	call site: 00073	os.path.join
6	143	git.repo.base.Repo.__init__	call site: 00143	git.repo.fun.find_worktree_git_dir
5	190	...gitpython.fuzzing.fuzz-targets.fuzz_diff.TestOneInput	call site: 00190	fdp.ConsumeBytes
3	94	git.repo.base.Repo._get_config_path	call site: 00094	git.types.assert_never

Runtime coverage analysis

Covered functions

423

Functions that are reachable but not covered

161

Reachable functions

196

Percentage of reachable functions covered

17.86%

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	37
git.util	72
git.cmd	30
git.repo.fun	20
git.config	15
git.db	1
git.diff	41
git.objects.util	4
git.objects.base	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	125	57.3%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	93	42.6%
All colors	218	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
48	5	git.util.expand_path	call site: 00005	subprocess.Popen.head.commit.object.tree.resolve
34	69	git.util.is_cygwin_git	call site: 00069	git.util._is_cygwin_git
14	148	git.config.GitConfigParser.__init__	call site: 00148	git.config.get_config_path
6	120	git.repo.fun.is_git_dir	call site: 00120	os.path.join
6	190	git.repo.base.Repo.__init__	call site: 00190	git.repo.fun.find_worktree_git_dir
3	141	git.repo.base.Repo._get_config_path	call site: 00141	git.types.assert_never
2	129	git.repo.base.Repo.__init__	call site: 00129	git.repo.base.Repo._get_config_path
2	173	git.repo.base.Repo.__init__	call site: 00173	configparser.RawConfigParser.get
1	58	git.repo.base.Repo.init	call site: 00058	os.makedirs
1	65	git.repo.base.Repo.__init__	call site: 00065	os.getcwd
1	105	git.repo.base.Repo.__init__	call site: 00105	.str
1	107	git.repo.base.Repo.__init__	call site: 00107	warnings.warn

Runtime coverage analysis

Covered functions

423

Functions that are reachable but not covered

115

Reachable functions

138

Percentage of reachable functions covered

16.67%

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

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	188	65.9%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	97	34.0%
All colors	285	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
64	5	git.util.expand_path	call site: 00005	git.cmd.Popen.object.head.commit.tree.resolve
44	240	...gitpython.fuzzing.fuzz-targets.fuzz_submodule.TestOneInput	call site: 00240	...gitpython.fuzzing.fuzz-targets.fuzz_submodule.sanitize_input
34	85	git.util.is_cygwin_git	call site: 00085	git.util._is_cygwin_git
14	164	git.config.GitConfigParser.__init__	call site: 00164	git.config.get_config_path
6	136	git.repo.fun.is_git_dir	call site: 00136	os.path.join
6	206	git.repo.base.Repo.__init__	call site: 00206	git.repo.fun.find_worktree_git_dir
3	157	git.repo.base.Repo._get_config_path	call site: 00157	git.types.assert_never
3	230	...gitpython.fuzzing.fuzz-targets.fuzz_submodule.TestOneInput	call site: 00230	...gitpython.fuzzing.fuzz-targets.fuzz_submodule.sanitize_input
2	145	git.repo.base.Repo.__init__	call site: 00145	git.repo.base.Repo._get_config_path
2	189	git.repo.base.Repo.__init__	call site: 00189	configparser.RawConfigParser.get
1	74	git.repo.base.Repo.init	call site: 00074	os.makedirs
1	81	git.repo.base.Repo.__init__	call site: 00081	os.getcwd

Runtime coverage analysis

Covered functions

422

Functions that are reachable but not covered

153

Reachable functions

176

Percentage of reachable functions covered

13.07%

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	37
git.util	99
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	21	12.2%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	151	87.7%
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
15	142	git.config.GitConfigParser._included_paths	call site: 00142	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

422

Functions that are reachable but not covered

144

Reachable functions

151

Percentage of reachable functions covered

4.64%

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	148

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	2.17%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	225	97.8%
All colors	230	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	142	...gitpython.fuzzing.fuzz-targets.fuzz_repo.TestOneInput	call site: 00142	os.path.join
1	0	EP	call site: 00000	atheris.FuzzedDataProvider

Runtime coverage analysis

Covered functions

423

Functions that are reachable but not covered

222

Reachable functions

226

Percentage of reachable functions covered

1.77%

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	154
git.objects.tree	2
git.objects.fun	4
git.compat	65

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']	12	0	22	26	13	310	1	1014	514

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

Functions statically reachable by fuzzers

94 / 661

Cyclomatic complexity statically reachable by fuzzers

395 / 2331

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

/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_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.expand_path', '...gitpython.fuzzing.fuzz-targets.fuzz_submodule.TestOneInput', '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']

/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']

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

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

Directories in report

Directory