High level conclusions

Fuzzers reach 54.80% code coverage.

Fuzzer fuzz_config is blocked:

The runtime code coverage of fuzz_config covers 1.988% 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 0.785% 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.52% 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 16.19% 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.34% 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

52 / 655

Cyclomatic complexity statically reachable by fuzzers

222 / 2311

Runtime code coverage of functions

359 / 655

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	244	60.8%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	157	39.1%
All colors	401	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
42	251	git.cmd.handle_process_output	call site: 00251	git.util.RemoteProgress.new_message_handler.handler
34	40	git.util.is_cygwin_git	call site: 00040	git.util._is_cygwin_git
25	350	git.util.finalize_process	call site: 00350	git.diff.Diff.__init__
24	376	...gitpython.fuzzing.fuzz-targets.fuzz_diff.BytesProcessAdapter.__init__	call site: 00376	git.diff.Diff._handle_diff_line
22	215	...gitpython.fuzzing.fuzz-targets.fuzz_diff.TestOneInput	call site: 00215	git.diff.Diff._index_from_patch_format
19	5	git.util.expand_path	call site: 00005	datetime.timedelta.resolve
14	119	git.config.GitConfigParser.__init__	call site: 00119	git.config.get_config_path
14	316	git.util.RemoteProgress._parse_progress_line	call site: 00316	git.util.finalize_process
7	196	git.objects.base.IndexObject.__init__	call site: 00196	git.objects.base.IndexObject.__init__
6	91	git.repo.fun.is_git_dir	call site: 00091	os.path.join
6	161	git.repo.base.Repo.__init__	call site: 00161	git.repo.fun.find_worktree_git_dir
5	206	...gitpython.fuzzing.fuzz-targets.fuzz_diff.TestOneInput	call site: 00206	fdp.ConsumeBytes

Runtime coverage analysis

Covered functions

417

Functions that are reachable but not covered

215

Reachable functions

251

Percentage of reachable functions covered

14.34%

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	105
git.cmd	54
git.repo.fun	20
git.config	15
git.db	1
git.diff	40
git.objects.util	4
git.objects.base	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	154	61.3%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	97	38.6%
All colors	251	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	206	...gitpython.fuzzing.fuzz-targets.fuzz_submodule.TestOneInput	call site: 00206	...gitpython.fuzzing.fuzz-targets.fuzz_submodule.sanitize_input
34	51	git.util.is_cygwin_git	call site: 00051	git.util._is_cygwin_git
30	5	git.util.expand_path	call site: 00005	git.cmd.Popen.resolve
14	130	git.config.GitConfigParser.__init__	call site: 00130	git.config.get_config_path
6	102	git.repo.fun.is_git_dir	call site: 00102	os.path.join
6	172	git.repo.base.Repo.__init__	call site: 00172	git.repo.fun.find_worktree_git_dir
3	123	git.repo.base.Repo._get_config_path	call site: 00123	git.types.assert_never
3	196	...gitpython.fuzzing.fuzz-targets.fuzz_submodule.TestOneInput	call site: 00196	...gitpython.fuzzing.fuzz-targets.fuzz_submodule.sanitize_input
2	111	git.repo.base.Repo.__init__	call site: 00111	git.repo.base.Repo._get_config_path
2	155	git.repo.base.Repo.__init__	call site: 00155	configparser.RawConfigParser.get
1	40	git.repo.base.Repo.init	call site: 00040	os.makedirs
1	47	git.repo.base.Repo.__init__	call site: 00047	os.getcwd

Runtime coverage analysis

Covered functions

416

Functions that are reachable but not covered

119

Reachable functions

142

Percentage of reachable functions covered

16.2%

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	65
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	157	62.8%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	93	37.2%
All colors	250	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
80	5	git.util.expand_path	call site: 00005	subprocess.Popen.tree.object.head.commit.resolve
34	101	git.util.is_cygwin_git	call site: 00101	git.util._is_cygwin_git
14	180	git.config.GitConfigParser.__init__	call site: 00180	git.config.get_config_path
6	152	git.repo.fun.is_git_dir	call site: 00152	os.path.join
6	222	git.repo.base.Repo.__init__	call site: 00222	git.repo.fun.find_worktree_git_dir
3	173	git.repo.base.Repo._get_config_path	call site: 00173	git.types.assert_never
2	161	git.repo.base.Repo.__init__	call site: 00161	git.repo.base.Repo._get_config_path
2	205	git.repo.base.Repo.__init__	call site: 00205	configparser.RawConfigParser.get
1	90	git.repo.base.Repo.init	call site: 00090	os.makedirs
1	97	git.repo.base.Repo.__init__	call site: 00097	os.getcwd
1	137	git.repo.base.Repo.__init__	call site: 00137	.str
1	139	git.repo.base.Repo.__init__	call site: 00139	warnings.warn

Runtime coverage analysis

Covered functions

417

Functions that are reachable but not covered

147

Reachable functions

170

Percentage of reachable functions covered

13.53%

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

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	7	1.81%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	379	98.1%
All colors	386	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	182	...gitpython.fuzzing.fuzz-targets.fuzz_repo.TestOneInput	call site: 00182	os.path.join
2	196	...gitpython.fuzzing.fuzz-targets.fuzz_repo.TestOneInput	call site: 00196	git.objects.fun.tree_entries_from_data
1	0	EP	call site: 00000	atheris.FuzzedDataProvider

Runtime coverage analysis

Covered functions

417

Functions that are reachable but not covered

379

Reachable functions

382

Percentage of reachable functions covered

0.79%

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

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	140	22.8%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	473	77.1%
All colors	613	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
125	482	git.config.GitConfigParser.read	call site: 00482	datetime.timedelta.object.tree
13	464	git.config.GitConfigParser._included_paths	call site: 00464	git.config.GitConfigParser.items
1	1	...gitpython.fuzzing.fuzz-targets.fuzz_config.TestOneInput	call site: 00001	git.config.GitConfigParser.read
1	611	git.config.GitConfigParser.read	call site: 00611	.str

Runtime coverage analysis

Covered functions

416

Functions that are reachable but not covered

345

Reachable functions

352

Percentage of reachable functions covered

1.99%

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	349

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.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']	6	0	20	24	13	310	0	984	751

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

Functions statically reachable by fuzzers

81 / 655

Cyclomatic complexity statically reachable by fuzzers

349 / 2311

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.cmd.handle_process_output', '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.util.expand_path', 'git.config.GitConfigParser.__init__', 'git.util.RemoteProgress._parse_progress_line', 'git.objects.base.IndexObject.__init__', 'git.repo.fun.is_git_dir']

/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', '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.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.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_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_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.read', 'git.config.GitConfigParser._included_paths', '...gitpython.fuzzing.fuzz-targets.fuzz_config.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_repo', 'fuzz_blob', 'fuzz_submodule', 'fuzz_config', 'fuzz_diff']
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	39	20	51.28%	['fuzz_repo', 'fuzz_blob', 'fuzz_diff', 'fuzz_config']
git.cmd.handle_process_output.pump_stream	51	28	54.90%	['fuzz_repo', 'fuzz_blob', 'fuzz_submodule', 'fuzz_config', 'fuzz_diff']
git.cmd.Git.refresh	35	12	34.28%	['fuzz_repo', 'fuzz_blob', 'fuzz_submodule', 'fuzz_config', 'fuzz_diff']
git.cmd.Git.execute.communicate	34	16	47.05%	['fuzz_repo', 'fuzz_blob', 'fuzz_submodule', 'fuzz_config', 'fuzz_diff']
git.remote.PushInfo._from_line	32	0	0.0%	[]
git.objects.commit.Commit._deserialize	55	28	50.90%	['fuzz_repo', 'fuzz_blob', 'fuzz_submodule', 'fuzz_config', 'fuzz_diff']
git.util.RemoteProgress._parse_progress_line	44	12	27.27%	['fuzz_repo', 'fuzz_blob', 'fuzz_submodule', 'fuzz_config', 'fuzz_diff']
git.objects.util.parse_date	46	9	19.56%	['fuzz_repo', 'fuzz_blob', 'fuzz_submodule', 'fuzz_config', 'fuzz_diff']
git.objects.submodule.base.Submodule.add	56	30	53.57%	['fuzz_repo', 'fuzz_blob', 'fuzz_submodule', 'fuzz_config', 'fuzz_diff']
git.objects.submodule.base.Submodule.update	94	46	48.93%	['fuzz_repo', 'fuzz_blob', 'fuzz_submodule', 'fuzz_config', 'fuzz_diff']
git.objects.submodule.base.Submodule.move	49	0	0.0%	[]
git.objects.submodule.base.Submodule.remove	60	0	0.0%	[]
stream.read	300	141	47.0%	['fuzz_repo', 'fuzz_blob', 'fuzz_diff', 'fuzz_config']
git.repo.fun.rev_parse	100	40	40.0%	['fuzz_repo', 'fuzz_blob', 'fuzz_submodule', 'fuzz_config', 'fuzz_diff']
git.index.base.IndexFile.checkout.handle_stderr	49	0	0.0%	[]
f.readline	56	20	35.71%	['fuzz_repo', 'fuzz_blob', 'fuzz_submodule', 'fuzz_config', 'fuzz_diff']
s.encode	67	32	47.76%	['fuzz_repo', 'fuzz_blob', 'fuzz_submodule', 'fuzz_config', 'fuzz_diff']
buf.find	70	16	22.85%	['fuzz_repo', 'fuzz_blob', 'fuzz_submodule', 'fuzz_config', 'fuzz_diff']
git.index.fun.aggressive_tree_merge	36	0	0.0%	[]
git.objects.submodule.root.RootModule.update	104	26	25.0%	['fuzz_repo', 'fuzz_blob', 'fuzz_submodule', 'fuzz_config', 'fuzz_diff']
ref.set_reference	45	10	22.22%	['fuzz_repo', 'fuzz_blob', 'fuzz_submodule', 'fuzz_config', 'fuzz_diff']

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

Directories in report

Directory