High level conclusions

Fuzzers reach 51.06% code coverage.

Fuzzer fuzz_blob is blocked:

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

Fuzzer fuzz_diff is blocked:

The runtime code coverage of fuzz_diff covers 1.918% 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 13.13% 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 6.25% 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

56 / 660

Cyclomatic complexity statically reachable by fuzzers

236 / 2328

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_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	128	57.6%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	94	42.3%
All colors	222	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	177	...gitpython.fuzzing.fuzz-targets.fuzz_submodule.TestOneInput	call site: 00177	...gitpython.fuzzing.fuzz-targets.fuzz_submodule.sanitize_input
34	22	git.util.is_cygwin_git	call site: 00022	git.util._is_cygwin_git
14	101	git.config.GitConfigParser.__init__	call site: 00101	git.config.get_config_path
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
3	94	git.repo.base.Repo._get_config_path	call site: 00094	git.types.assert_never
3	137	git.repo.fun.find_submodule_git_dir	call site: 00137	os.path.dirname
3	167	...gitpython.fuzzing.fuzz-targets.fuzz_submodule.TestOneInput	call site: 00167	...gitpython.fuzzing.fuzz-targets.fuzz_submodule.sanitize_input
2	82	git.repo.base.Repo.__init__	call site: 00082	git.repo.base.Repo._get_config_path
2	126	git.repo.base.Repo.__init__	call site: 00126	configparser.RawConfigParser.get
1	5	git.util.expand_path	call site: 00005	p.resolve
1	11	git.repo.base.Repo.init	call site: 00011	os.makedirs

Runtime coverage analysis

Covered functions

388

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	37
git.util	36
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	49	25.9%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	140	74.0%
All colors	189	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
32	151	git.config.GitConfigParser.read	call site: 00151	typing.IO.head.commit.object
15	131	git.config.GitConfigParser._included_paths	call site: 00131	git.config.GitConfigParser.items
1	1	...gitpython.fuzzing.fuzz-targets.fuzz_config.TestOneInput	call site: 00001	git.config.GitConfigParser.read
1	187	git.config.GitConfigParser.read	call site: 00187	.str

Runtime coverage analysis

Covered functions

388

Functions that are reachable but not covered

105

Reachable functions

112

Percentage of reachable functions covered

6.25%

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	109

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	181	63.9%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	102	36.0%
All colors	283	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
96	5	git.util.expand_path	call site: 00005	subprocess.Popen.object.resolve
34	117	git.util.is_cygwin_git	call site: 00117	git.util._is_cygwin_git
14	196	git.config.GitConfigParser.__init__	call site: 00196	git.config.get_config_path
6	168	git.repo.fun.is_git_dir	call site: 00168	os.path.join
6	238	git.repo.base.Repo.__init__	call site: 00238	git.repo.fun.find_worktree_git_dir
5	257	git.db.GitCmdObjectDB.__init__	call site: 00257	git.db.GitCmdObjectDB.__init__
3	189	git.repo.base.Repo._get_config_path	call site: 00189	git.types.assert_never
3	232	git.repo.fun.find_submodule_git_dir	call site: 00232	os.path.dirname
2	177	git.repo.base.Repo.__init__	call site: 00177	git.repo.base.Repo._get_config_path
2	221	git.repo.base.Repo.__init__	call site: 00221	configparser.RawConfigParser.get
1	0	EP	call site: 00000	atheris.FuzzedDataProvider
1	106	git.repo.base.Repo.init	call site: 00106	os.makedirs

Runtime coverage analysis

Covered functions

389

Functions that are reachable but not covered

172

Reachable functions

198

Percentage of reachable functions covered

13.13%

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	131
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_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	563	73.9%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	198	26.0%
All colors	761	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
388	148	...gitpython.fuzzing.fuzz-targets.fuzz_diff.TestOneInput	call site: 00148	git.diff.Diff._index_from_patch_format
158	602	git.util.finalize_process	call site: 00602	git.diff.Diff._handle_diff_line
7	129	git.objects.base.IndexObject.__init__	call site: 00129	git.objects.base.IndexObject.__init__
5	139	...gitpython.fuzzing.fuzz-targets.fuzz_diff.TestOneInput	call site: 00139	fdp.ConsumeBytes
3	123	git.diff.Diff.__init__	call site: 00123	a_rawpath.decode
1	67	...gitpython.fuzzing.fuzz-targets.fuzz_diff.TestOneInput	call site: 00067	git.diff.Diff.__init__
1	76	git.objects.util.mode_str_to_int	call site: 00076	io.BytesIO

Runtime coverage analysis

Covered functions

389

Functions that are reachable but not covered

460

Reachable functions

469

Percentage of reachable functions covered

1.92%

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	144
git.diff	85
git.objects.util	49
git.objects.base	1
git.cmd	188
git.util	145

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	0	0.0%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	296	100.%
All colors	296	100

Runtime coverage analysis

Covered functions

389

Functions that are reachable but not covered

295

Reachable functions

295

Percentage of reachable functions covered

0.0%

NB: The sum of covered functions and functions that are reachable but not covered need not be equal to Reachable functions . This is because the reachability analysis is an approximation and thus at runtime some functions may be covered that are not included in the reachability analysis. This is a limitation of our static analysis capabilities.

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

Function name	source code lines	source lines hit	percentage hit

Files reached

filename	functions hit
/	1
...gitpython.fuzzing.fuzz-targets.fuzz_blob	294

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	241	1	807	430

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

Functions statically reachable by fuzzers

93 / 660

Cyclomatic complexity statically reachable by fuzzers

392 / 2328

All functions overview

If you implement fuzzers for these functions, the status of all functions in the project will be:

Func name	Functions filename	Args	Function call depth	Reached by Fuzzers	Runtime reached by Fuzzers	Combined reached by Fuzzers	Fuzzers runtime hit	Func lines hit %	I Count	BB Count	Cyclomatic complexity	Functions reached	Reached by functions	Accumulated cyclomatic complexity	Undiscovered complexity

This sections provides heuristics that can be used as input to a fuzz engine when running a given fuzz target. The current focus is on providing input that is usable by libFuzzer.

/src/gitpython/fuzzing/fuzz-targets/fuzz_submodule.py

Dictionary

Use this with the libFuzzer -dict=DICT.file flag

Fuzzer function priority

Use one of these functions as input to libfuzzer with flag: -focus_function name

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

/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.expand_path', 'git.util.is_cygwin_git', '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_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

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_blob', 'fuzz_submodule', 'fuzz_repo', 'fuzz_diff', 'fuzz_config']
git.repo.base.Repo.blame_incremental	39	0	0.0%	[]
git.repo.base.Repo.blame	75	0	0.0%	[]
repo.git.read_tree	39	17	43.58%	['fuzz_blob', 'fuzz_submodule', 'fuzz_repo', 'fuzz_diff', 'fuzz_config']
submodule.module_exists	64	29	45.31%	['fuzz_diff', 'fuzz_submodule']
git.objects.submodule	39	20	51.28%	['fuzz_repo', 'fuzz_diff', 'fuzz_blob', 'fuzz_submodule']
git.cmd.handle_process_output.pump_stream	51	2	3.921%	['fuzz_blob', 'fuzz_submodule', 'fuzz_repo', 'fuzz_diff', 'fuzz_config']
git.cmd.Git.refresh	35	12	34.28%	['fuzz_blob', 'fuzz_submodule', 'fuzz_repo', 'fuzz_diff', 'fuzz_config']
git.cmd.Git.execute.communicate	34	16	47.05%	['fuzz_blob', 'fuzz_submodule', 'fuzz_repo', 'fuzz_diff', 'fuzz_config']
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%	[]
git.index.base.IndexFile.checkout.handle_stderr	49	0	0.0%	[]
git.objects.util.parse_date	46	2	4.347%	['fuzz_blob', 'fuzz_submodule', 'fuzz_repo', 'fuzz_diff', 'fuzz_config']
git.objects.commit.Commit._deserialize	55	28	50.90%	['fuzz_blob', 'fuzz_submodule', 'fuzz_repo', 'fuzz_diff', 'fuzz_config']
git.util.RemoteProgress._parse_progress_line	44	0	0.0%	['fuzz_diff']
git.objects.submodule.base.Submodule.add	56	30	53.57%	['fuzz_blob', 'fuzz_submodule', 'fuzz_repo', 'fuzz_diff', 'fuzz_config']
git.objects.submodule.base.Submodule.update	97	13	13.40%	['fuzz_blob', 'fuzz_submodule', 'fuzz_repo', 'fuzz_diff', 'fuzz_config']
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_blob', 'fuzz_submodule', 'fuzz_repo', 'fuzz_diff', 'fuzz_config']
git.repo.fun.rev_parse	100	22	22.0%	['fuzz_blob', 'fuzz_submodule', 'fuzz_repo', 'fuzz_diff', 'fuzz_config']
git.config.GitConfigParser._included_paths	33	8	24.24%	['fuzz_blob', 'fuzz_submodule', 'fuzz_repo', 'fuzz_diff', 'fuzz_config']
f.readline	56	20	35.71%	['fuzz_blob', 'fuzz_submodule', 'fuzz_repo', 'fuzz_diff', 'fuzz_config']
ref.set_reference	45	10	22.22%	['fuzz_blob', 'fuzz_submodule', 'fuzz_repo', 'fuzz_diff', 'fuzz_config']
git.objects.submodule.root.RootModule.update	104	0	0.0%	[]
buf.find	70	16	22.85%	['fuzz_blob', 'fuzz_submodule', 'fuzz_repo', 'fuzz_diff', 'fuzz_config']
git.diff.Diffable.diff	39	5	12.82%	['fuzz_blob', 'fuzz_submodule', 'fuzz_repo', 'fuzz_diff', '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.index.fun.aggressive_tree_merge	36	0	0.0%	[]

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

Directories in report

Directory