High level conclusions

Fuzzers reach 51.06% code coverage.

Fuzzer fuzz_blob is blocked:

The runtime code coverage of fuzz_blob covers 3.019% 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 1.744% 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_config is blocked:

The runtime code coverage of fuzz_config covers 8.333% 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 20.14% 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

68 / 660

Cyclomatic complexity statically reachable by fuzzers

291 / 2327

Runtime code coverage of functions

337 / 660

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_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	117	53.4%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	102	46.5%
All colors	219	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	53	git.util.is_cygwin_git	call site: 00053	git.util._is_cygwin_git
32	5	git.util.expand_path	call site: 00005	typing.BinaryIO.tree.head.commit.object.resolve
14	132	git.config.GitConfigParser.__init__	call site: 00132	git.config.get_config_path
6	104	git.repo.fun.is_git_dir	call site: 00104	os.path.join
6	174	git.repo.base.Repo.__init__	call site: 00174	git.repo.fun.find_worktree_git_dir
5	193	git.db.GitCmdObjectDB.__init__	call site: 00193	git.db.GitCmdObjectDB.__init__
3	125	git.repo.base.Repo._get_config_path	call site: 00125	git.types.assert_never
3	168	git.repo.fun.find_submodule_git_dir	call site: 00168	os.path.dirname
2	113	git.repo.base.Repo.__init__	call site: 00113	git.repo.base.Repo._get_config_path
2	157	git.repo.base.Repo.__init__	call site: 00157	configparser.RawConfigParser.get
1	0	EP	call site: 00000	atheris.FuzzedDataProvider
1	42	git.repo.base.Repo.init	call site: 00042	os.makedirs

Runtime coverage analysis

Covered functions

389

Functions that are reachable but not covered

107

Reachable functions

134

Percentage of reachable functions covered

20.15%

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	15
git.repo.base	37
git.util	67
git.cmd	3
git.repo.fun	20
git.config	15
git.db	1
git.objects.tree	2
git.objects.fun	4
git.compat	2

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	18.4%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	84	81.5%
All colors	103	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	75	git.config.GitConfigParser._included_paths	call site: 00075	git.config.GitConfigParser.items
4	93	git.config.GitConfigParser.read	call site: 00093	typing.cast
1	1	...gitpython.fuzzing.fuzz-targets.fuzz_config.TestOneInput	call site: 00001	git.config.GitConfigParser.read
1	101	git.config.GitConfigParser.read	call site: 00101	.str

Runtime coverage analysis

Covered functions

388

Functions that are reachable but not covered

77

Reachable functions

84

Percentage of reachable functions covered

8.33%

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	81

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	191	67.0%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	94	32.9%
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	datetime.timedelta.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	200	git.repo.fun.find_submodule_git_dir	call site: 00200	os.path.dirname
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

Runtime coverage analysis

Covered functions

388

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_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	454	71.7%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	179	28.2%
All colors	633	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
306	121	...gitpython.fuzzing.fuzz-targets.fuzz_diff.TestOneInput	call site: 00121	git.diff.Diff._index_from_patch_format
131	501	git.util.finalize_process	call site: 00501	git.diff.Diff._handle_diff_line
7	102	git.objects.base.IndexObject.__init__	call site: 00102	git.objects.base.IndexObject.__init__
5	112	...gitpython.fuzzing.fuzz-targets.fuzz_diff.TestOneInput	call site: 00112	fdp.ConsumeBytes
3	96	git.diff.Diff.__init__	call site: 00096	a_rawpath.decode
1	75	...gitpython.fuzzing.fuzz-targets.fuzz_diff.TestOneInput	call site: 00075	git.diff.Diff.__init__
1	84	git.objects.util.mode_str_to_int	call site: 00084	io.BytesIO

Runtime coverage analysis

Covered functions

389

Functions that are reachable but not covered

507

Reachable functions

516

Percentage of reachable functions covered

1.74%

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	160
git.diff	50
git.objects.util	14
git.objects.base	1
git.cmd	169
git.util	160

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	1643	69.2%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	731	30.7%
All colors	2374	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
703	1079	git.repo.fun.rev_parse	call site: 01079	git.repo.base.Repo.__init__
135	123	git.util.is_cygwin_git	call site: 00123	git.util._is_cygwin_git
120	1984	git.config.GitConfigParser.__init__	call site: 01984	git.repo.base.Repo.__init__
110	750	git.repo.fun.name_to_object	call site: 00750	git.repo.fun.short_to_long
109	969	git.repo.fun.name_to_object	call site: 00969	git.repo.base.Repo.__init__
109	1871	git.repo.base.Repo._get_config_path	call site: 01871	git.repo.base.Repo.__init__
108	2258	git.repo.base.Repo.__init__	call site: 02258	git.repo.base.Repo.__init__
102	5	git.util.expand_path	call site: 00005	datetime.timedelta.tree.object.resolve
78	1783	git.repo.fun.rev_parse	call site: 01783	git.repo.base.Repo.__init__
29	284	git.repo.base.Repo.__init__	call site: 00284	git.refs.tag.TagReference.object
6	275	git.repo.fun.is_git_dir	call site: 00275	os.path.join
6	2132	git.repo.base.Repo.__init__	call site: 02132	git.repo.fun.find_worktree_git_dir

Runtime coverage analysis

Covered functions

389

Functions that are reachable but not covered

1060

Reachable functions

1093

Percentage of reachable functions covered

3.02%

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_blob	9
git.repo.base	142
git.util	238
git.cmd	3
git.repo.fun	607
git.refs.tag	1
git.refs.symbolic	104
git.objects.base	213
git.objects.tag	1
git.objects.tree	1
git.objects.commit	3
git.config	121
git.db	1

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']	10	0	22	25	13	730	1	2274	1392

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

Functions statically reachable by fuzzers

99 / 660

Cyclomatic complexity statically reachable by fuzzers

416 / 2327

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_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.util.is_cygwin_git', 'git.util.expand_path', 'git.config.GitConfigParser.__init__', 'git.repo.fun.is_git_dir', 'git.repo.base.Repo.__init__', 'git.db.GitCmdObjectDB.__init__', 'git.repo.base.Repo._get_config_path', 'git.repo.fun.find_submodule_git_dir']

/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_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', 'git.repo.fun.find_submodule_git_dir']

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

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

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%	[]
f.readline	56	20	35.71%	['fuzz_repo', 'fuzz_diff', 'fuzz_config', 'fuzz_blob', 'fuzz_submodule']
repo.git.read_tree	39	17	43.58%	['fuzz_repo', 'fuzz_diff', 'fuzz_submodule']
git.index	39	20	51.28%	['fuzz_repo', 'fuzz_diff']
git.cmd.handle_process_output.pump_stream	51	2	3.921%	['fuzz_repo', 'fuzz_diff', 'fuzz_config', 'fuzz_blob', 'fuzz_submodule']
git.cmd.Git.refresh	35	12	34.28%	['fuzz_repo', 'fuzz_diff', 'fuzz_config', 'fuzz_blob', 'fuzz_submodule']
git.cmd.Git.execute.communicate	34	16	47.05%	['fuzz_repo', 'fuzz_diff', 'fuzz_config', 'fuzz_blob', 'fuzz_submodule']
git.remote.PushInfo._from_line	32	0	0.0%	[]
git.remote.FetchInfo._from_line	56	0	0.0%	[]
git.remote.Remote._get_fetch_info_from_stderr	39	0	0.0%	[]
s.encode	67	32	47.76%	['fuzz_repo', 'fuzz_diff', 'fuzz_config', 'fuzz_blob', 'fuzz_submodule']
git.util.RemoteProgress._parse_progress_line	44	0	0.0%	['fuzz_diff']
stream.read	300	141	47.0%	['fuzz_repo', 'fuzz_diff']
git.objects.util.parse_date	46	2	4.347%	['fuzz_repo', 'fuzz_diff', 'fuzz_config', 'fuzz_blob', 'fuzz_submodule']
git.objects.commit.Commit._deserialize	55	28	50.90%	['fuzz_repo', 'fuzz_diff', 'fuzz_config', 'fuzz_blob', 'fuzz_submodule']
git.objects.submodule.base.Submodule.add	56	30	53.57%	['fuzz_repo', 'fuzz_diff', 'fuzz_config', 'fuzz_blob', 'fuzz_submodule']
git.objects.submodule.base.Submodule.update	94	13	13.82%	['fuzz_repo', 'fuzz_diff', 'fuzz_config', 'fuzz_blob', 'fuzz_submodule']
git.objects.submodule.base.Submodule.move	49	0	0.0%	[]
git.objects.submodule.base.Submodule.remove	60	0	0.0%	[]
submodule.module	64	29	45.31%	['fuzz_repo', 'fuzz_diff', 'fuzz_config', 'fuzz_blob', 'fuzz_submodule']
git.repo.fun.rev_parse	100	22	22.0%	['fuzz_repo', 'fuzz_diff', 'fuzz_config', 'fuzz_blob', 'fuzz_submodule']
git.index.base.IndexFile.checkout.handle_stderr	49	0	0.0%	[]
buf.find	70	16	22.85%	['fuzz_repo', 'fuzz_diff', 'fuzz_config', 'fuzz_blob', 'fuzz_submodule']
git.diff.Diffable.diff	39	5	12.82%	['fuzz_repo', 'fuzz_diff', 'fuzz_config', 'fuzz_blob', '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.objects.submodule.root.RootModule.update	104	0	0.0%	[]
git.index.fun.aggressive_tree_merge	36	0	0.0%	[]
ref.set_reference	45	10	22.22%	['fuzz_repo', 'fuzz_diff', 'fuzz_config', 'fuzz_blob', '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.repo.base	['fuzz_repo', 'fuzz_submodule', 'fuzz_blob']	[]
git.repo.fun	['fuzz_repo', 'fuzz_submodule', 'fuzz_blob']	[]
gc	[]	[]
utils	[]	[]
functools	[]	[]
git.diff	['fuzz_diff']	[]
inspect	[]	[]
git.refs.log	[]	[]
git.index.fun	[]	[]
shutil	[]	[]
pathlib	[]	[]
struct	[]	[]
enum	[]	[]
git.objects.submodule.root	[]	[]
git.objects.fun	['fuzz_repo']	[]
git.remote	[]	[]
io	[]	[]
git.db	['fuzz_repo', 'fuzz_submodule', 'fuzz_blob']	[]
binascii	[]	[]
weakref	[]	[]
os	[]	[]
typing	[]	[]
git.objects.tree	['fuzz_repo', 'fuzz_blob']	[]
git.util	['fuzz_repo', 'fuzz_submodule', 'fuzz_diff', 'fuzz_blob']	[]
fnmatch	[]	[]
git.refs.symbolic	['fuzz_blob']	[]
tempfile	[]	[]
logging	[]	[]
typing_extensions	[]	[]
git.objects.blob	[]	[]
git.refs.remote	[]	[]
uuid	[]	[]
git.types	[]	[]
...gitpython.fuzzing.fuzz-targets.fuzz_submodule	['fuzz_submodule']	[]
atheris	[]	[]
glob	[]	[]
contextlib	[]	[]
git.objects.submodule.base	[]	[]
git.objects.commit	['fuzz_blob']	[]
git.refs.head	[]	[]
git.objects	[]	[]
gitdb	[]	[]
mimetypes	[]	[]
...gitpython.fuzzing.fuzz-targets.fuzz_blob	['fuzz_blob']	[]
time	[]	[]
git.exc	[]	[]
subprocess	[]	[]
git.objects.submodule.util	[]	[]
git.config	['fuzz_repo', 'fuzz_config', 'fuzz_submodule', 'fuzz_blob']	[]
datetime	[]	[]
calendar	[]	[]
re	[]	[]
textwrap	[]	[]
...gitpython.fuzzing.fuzz-targets.fuzz_repo	['fuzz_repo']	[]
git.compat	['fuzz_repo']	[]
git.objects.submodule	[]	[]
platform	[]	[]
git.objects.tag	['fuzz_blob']	[]
	[]	[]
git.objects.util	['fuzz_diff']	[]
shlex	[]	[]
git.index	[]	[]
git.refs	[]	[]
getpass	[]	[]
git	[]	[]
itertools	[]	[]
warnings	[]	[]
collections	[]	[]
git.index.util	[]	[]
sys	[]	[]
urllib	[]	[]
importlib	[]	[]
configparser	[]	[]
threading	[]	[]
git.index.base	[]	[]
...gitpython.fuzzing.fuzz-targets.fuzz_config	['fuzz_config']	[]
git.repo	[]	[]
git.index.typ	[]	[]
git.cmd	['fuzz_repo', 'fuzz_submodule', 'fuzz_diff', 'fuzz_blob']	[]
git.objects.base	['fuzz_diff', 'fuzz_blob']	[]
git.refs.tag	['fuzz_blob']	[]
git.refs.reference	[]	[]
stat	[]	[]
locale	[]	[]
...gitpython.fuzzing.fuzz-targets.fuzz_diff	['fuzz_diff']	[]

Directories in report

Directory