High level conclusions

Fuzzers reach 52.95% code coverage.

Fuzzer fuzz_submodule is blocked:

The runtime code coverage of fuzz_submodule covers 6.666% 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 4.081% 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 14.28% 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 18.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 15.81% 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

67 / 661

Cyclomatic complexity statically reachable by fuzzers

289 / 2332

Runtime code coverage of functions

350 / 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	216	59.1%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	149	40.8%
All colors	365	100

Fuzz blockers

The following nodes represent call sites where fuzz blockers occur.

Amount of callsites blocked	Calltree index	Parent function	Callsite	Largest blocked function
34	22	git.util.is_cygwin_git	call site: 00022	git.util._is_cygwin_git
34	233	git.cmd.handle_process_output	call site: 00233	git.util.RemoteProgress.new_message_handler.handler
25	314	git.util.finalize_process	call site: 00314	git.diff.Diff.__init__
24	340	...gitpython.fuzzing.fuzz-targets.fuzz_diff.BytesProcessAdapter.__init__	call site: 00340	git.diff.Diff._handle_diff_line
22	197	...gitpython.fuzzing.fuzz-targets.fuzz_diff.TestOneInput	call site: 00197	git.diff.Diff._index_from_patch_format
14	101	git.config.GitConfigParser.__init__	call site: 00101	git.config.get_config_path
12	272	git.util.RemoteProgress._parse_progress_line	call site: 00272	git.util.finalize_process
7	178	git.objects.base.IndexObject.__init__	call site: 00178	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	188	...gitpython.fuzzing.fuzz-targets.fuzz_diff.TestOneInput	call site: 00188	fdp.ConsumeBytes
3	94	git.repo.base.Repo._get_config_path	call site: 00094	git.types.assert_never

Runtime coverage analysis

Covered functions

404

Functions that are reachable but not covered

181

Reachable functions

215

Percentage of reachable functions covered

15.81%

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	77
git.cmd	46
git.repo.fun	20
git.config	15
git.db	1
git.diff	40
git.objects.util	4
git.objects.base	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	130	55.3%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	105	44.6%
All colors	235	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	typing.IO.tree.object.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
5	209	git.db.GitCmdObjectDB.__init__	call site: 00209	git.db.GitCmdObjectDB.__init__
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	0	EP	call site: 00000	atheris.FuzzedDataProvider
1	58	git.repo.base.Repo.init	call site: 00058	os.makedirs
1	65	git.repo.base.Repo.__init__	call site: 00065	os.getcwd

Runtime coverage analysis

Covered functions

404

Functions that are reachable but not covered

123

Reachable functions

150

Percentage of reachable functions covered

18.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_repo	15
git.repo.base	37
git.util	83
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	21	27.2%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	56	72.7%
All colors	77	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	47	git.config.GitConfigParser._included_paths	call site: 00047	git.config.GitConfigParser.items
4	67	git.config.GitConfigParser.read	call site: 00067	typing.cast
1	1	...gitpython.fuzzing.fuzz-targets.fuzz_config.TestOneInput	call site: 00001	git.config.GitConfigParser.read
1	75	git.config.GitConfigParser.read	call site: 00075	.str

Runtime coverage analysis

Covered functions

403

Functions that are reachable but not covered

48

Reachable functions

56

Percentage of reachable functions covered

14.29%

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	53

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	555	43.7%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	715	56.2%
All colors	1270	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
130	1132	git.repo.base.Repo.__init__	call site: 01132	git.repo.base.Repo.commit
98	382	git.repo.fun.name_to_object	call site: 00382	git.repo.fun.short_to_long
94	5	git.util.expand_path	call site: 00005	git.cmd.Popen.object.tree.head.commit.resolve
54	574	git.repo.fun.name_to_object	call site: 00574	git.repo.base.Repo.tree
48	981	git.repo.fun.rev_parse	call site: 00981	git.repo.base.Repo.__init__
47	929	git.objects.base.Object.new_from_sha	call site: 00929	git.repo.base.Repo.__init__
34	115	git.util.is_cygwin_git	call site: 00115	git.util._is_cygwin_git
14	194	git.config.GitConfigParser.__init__	call site: 00194	git.repo.base.Repo.__init__
6	166	git.repo.fun.is_git_dir	call site: 00166	os.path.join
6	236	git.repo.base.Repo.__init__	call site: 00236	git.repo.fun.find_worktree_git_dir
3	187	git.repo.base.Repo._get_config_path	call site: 00187	git.repo.base.Repo.__init__
3	730	git.objects.commit.Commit.__init__	call site: 00730	git.objects.tag.TagObject.__init__

Runtime coverage analysis

Covered functions

404

Functions that are reachable but not covered

799

Reachable functions

833

Percentage of reachable functions covered

4.08%

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	164
git.util	129
git.cmd	3
git.repo.fun	445
git.config	15
git.refs.tag	1
git.refs.symbolic	97
git.objects.base	194
git.objects.commit	3
git.objects.tag	1
git.objects.tree	1
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	217	36.5%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	376	63.4%
All colors	593	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
62	28	git.util.expand_path	call site: 00028	datetime.timedelta.head.commit.resolve
44	548	...gitpython.fuzzing.fuzz-targets.fuzz_submodule.TestOneInput	call site: 00548	...gitpython.fuzzing.fuzz-targets.fuzz_submodule.sanitize_input
34	146	git.util.is_cygwin_git	call site: 00146	git.util._is_cygwin_git
26	229	git.repo.base.Repo._get_config_path	call site: 00229	git.types.assert_never
14	290	git.config.GitConfigParser.__init__	call site: 00290	git.config.get_config_path
10	209	git.repo.base.Repo.__init__	call site: 00209	git.repo.base.Repo._get_config_path
6	197	git.repo.fun.is_git_dir	call site: 00197	os.path.join
6	360	git.repo.base.Repo.__init__	call site: 00360	git.repo.fun.find_worktree_git_dir
3	538	...gitpython.fuzzing.fuzz-targets.fuzz_submodule.TestOneInput	call site: 00538	...gitpython.fuzzing.fuzz-targets.fuzz_submodule.sanitize_input
2	343	git.repo.base.Repo.__init__	call site: 00343	configparser.RawConfigParser.get
1	95	git.repo.base.Repo.init	call site: 00095	os.makedirs
1	142	git.repo.base.Repo.__init__	call site: 00142	os.getcwd

Runtime coverage analysis

Covered functions

403

Functions that are reachable but not covered

336

Reachable functions

360

Percentage of reachable functions covered

6.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_submodule	63
git.repo.base	192
git.util	97
git.cmd	3
git.repo.fun	20
git.config	15
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']	11	0	22	26	13	621	1	1947	1056
git.refs.symbolic.SymbolicReference.set_reference	git.refs.symbolic	3	['N/A', 'N/A', 'N/A']	2	0	6	6	5	108	0	330	318
git.config.GitConfigParser.write	git.config	1	['N/A']	4	0	8	6	5	121	0	374	290

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

Functions statically reachable by fuzzers

104 / 661

Cyclomatic complexity statically reachable by fuzzers

437 / 2332

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.cmd.handle_process_output', 'git.util.finalize_process', '...gitpython.fuzzing.fuzz-targets.fuzz_diff.BytesProcessAdapter.__init__', '...gitpython.fuzzing.fuzz-targets.fuzz_diff.TestOneInput', '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_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']

/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_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.base.Repo.__init__', 'git.repo.fun.name_to_object', 'git.util.expand_path', 'git.repo.fun.rev_parse', 'git.objects.base.Object.new_from_sha', 'git.util.is_cygwin_git', 'git.config.GitConfigParser.__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=['git.util.expand_path', '...gitpython.fuzzing.fuzz-targets.fuzz_submodule.TestOneInput', 'git.util.is_cygwin_git', 'git.repo.base.Repo._get_config_path', 'git.config.GitConfigParser.__init__', 'git.repo.base.Repo.__init__', 'git.repo.fun.is_git_dir']

This section shows analysis of runtime coverage data.

For futher technical details on how this section is generated, please see the Glossary .

Complex functions with low coverage

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

Directories in report

Directory