High level conclusions

Fuzzer fuzz_object_store is blocked:

The runtime code coverage of fuzz_object_store covers 27.27% 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_configfile is blocked:

The runtime code coverage of fuzz_configfile covers 22.85% 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_bundle is blocked:

The runtime code coverage of fuzz_bundle covers 2.803% 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

96 / 1943

Cyclomatic complexity statically reachable by fuzzers

347 / 6911

Runtime code coverage of functions

289 / 1943

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_bundle

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	166	90.7%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	17	9.28%
All colors	183	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
99	10	...dulwich.fuzzing.fuzz-targets.fuzz_bundle.TestOneInput	call site: 00010	dulwich.pack.pack_objects_to_data
42	123	dulwich.file.GitFile	call site: 00123	dulwich.bundle.write_bundle
8	173	dulwich.bundle._read_bundle	call site: 00173	dulwich.bundle._read_bundle
7	1	...dulwich.fuzzing.fuzz-targets.fuzz_bundle.TestOneInput	call site: 00001	test_utils.EnhancedFuzzedDataProvider.PickValueInList
4	110	...dulwich.fuzzing.fuzz-targets.fuzz_bundle.TestOneInput	call site: 00110	dulwich.pack.PackData.from_file
3	169	dulwich.bundle._read_bundle	call site: 00169	line.startswith
2	166	...dulwich.fuzzing.fuzz-targets.fuzz_bundle.TestOneInput	call site: 00166	dulwich.bundle._read_bundle
1	118	dulwich.file._GitFile.__init__	call site: 00118	.getattr

Runtime coverage analysis

Covered functions

317

Functions that are reachable but not covered

104

Reachable functions

107

Percentage of reachable functions covered

2.8%

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
...dulwich.fuzzing.fuzz-targets.fuzz_bundle	13
dulwich.pack	73
dulwich.file	8
dulwich.contrib.swift	6
dulwich.bundle	18

Fuzzer: fuzz_configfile

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	1	1.31%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	75	98.6%
All colors	76	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
1	5	dulwich.config.ConfigFile.__init__	call site: 00005	included_paths.copy

Runtime coverage analysis

Covered functions

318

Functions that are reachable but not covered

27

Reachable functions

35

Percentage of reachable functions covered

22.86%

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

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

Function name	source code lines	source lines hit	percentage hit

Files reached

filename	functions hit
/	1
...dulwich.fuzzing.fuzz-targets.fuzz_configfile	3
dulwich.config	31

Fuzzer: fuzz_object_store

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	56	70.8%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	23	29.1%
All colors	79	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
26	27	...dulwich.fuzzing.fuzz-targets.fuzz_object_store.TestOneInput	call site: 00027	dulwich.patch.write_tree_diff
24	54	dulwich.objects.S_ISGITLINK	call site: 00054	dulwich.patch.write_object_diff.content
2	0	EP	call site: 00000	dulwich.repo.MemoryRepo.__init__
2	19	...dulwich.fuzzing.fuzz-targets.fuzz_object_store.TestOneInput	call site: 00019	dulwich.objects.Commit.__init__
2	23	...dulwich.fuzzing.fuzz-targets.fuzz_object_store.TestOneInput	call site: 00023	test_utils.EnhancedFuzzedDataProvider.ConsumeRandomBytes

Runtime coverage analysis

Covered functions

317

Functions that are reachable but not covered

32

Reachable functions

44

Percentage of reachable functions covered

27.27%

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
...dulwich.fuzzing.fuzz-targets.fuzz_object_store	12
dulwich.repo	4
dulwich.refs	2
dulwich.object_store	1
dulwich.config	2
dulwich.objects	4
dulwich.patch	23

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	112	39.2%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	173	60.7%
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
23	178	dulwich.config.StackedConfig.get	call site: 00178	dulwich.reftable.ReftableRefsContainer.__init__
16	241	dulwich.config.StackedConfig.default_backends	call site: 00241	dulwich.config.get_win_system_paths
13	161	dulwich.config.ConfigDict.items	call site: 00161	dulwich.object_store.DiskObjectStore.from_config
9	203	dulwich.repo.Repo.__init__	call site: 00203	dulwich.repo.parse_graftpoints
7	37	dulwich.repo.Repo.__init__	call site: 00037	os.path.isfile
7	263	dulwich.repo.Repo._init_maybe_bare	call site: 00263	test_utils.EnhancedFuzzedDataProvider.ConsumeRandomBytes
6	45	dulwich.repo.Repo.__init__	call site: 00045	dulwich.repo.read_gitfile
4	56	dulwich.repo.Repo.get_named_file	call site: 00056	os.path.join
4	274	...dulwich.fuzzing.fuzz-targets.fuzz_repo.TestOneInput	call site: 00274	repo.stage
4	280	...dulwich.fuzzing.fuzz-targets.fuzz_repo.TestOneInput	call site: 00280	test_utils.EnhancedFuzzedDataProvider.ConsumeRandomInt
3	0	EP	call site: 00000	dulwich.repo.Repo.init
3	10	dulwich.repo.Repo.init	call site: 00010	ctypes.WINFUNCTYPE

Runtime coverage analysis

Covered functions

317

Functions that are reachable but not covered

88

Reachable functions

126

Percentage of reachable functions covered

30.16%

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
...dulwich.fuzzing.fuzz-targets.fuzz_repo	17
dulwich.repo	45
dulwich.object_store	7
dulwich.refs	3
dulwich.config	64
dulwich.reftable	11
dulwich.objects	3
dulwich.hooks	2

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
dulwich.porcelain.clone	dulwich.porcelain	14	['N/A', 'N/A', 'N/A', 'N/A', 'N/A', 'N/A', 'N/A', 'N/A', 'N/A', 'N/A', 'N/A', 'N/A', 'N/A', 'N/A']	8	0	7	9	7	367	4	1210	813
dulwich.client.GitClient.clone	dulwich.client	13	['N/A', 'N/A', 'N/A', 'N/A', 'N/A', 'N/A', 'N/A', 'N/A', 'N/A', 'N/A', 'N/A', 'N/A', 'N/A']	8	0	10	12	8	390	0	1294	651
dulwich.porcelain.upload_pack	dulwich.porcelain	3	['N/A', 'N/A', 'N/A']	8	0	2	2	4	330	1	1093	489
dulwich.repo.BaseRepo.do_commit	dulwich.repo	14	['N/A', 'N/A', 'N/A', 'N/A', 'N/A', 'N/A', 'N/A', 'N/A', 'N/A', 'N/A', 'N/A', 'N/A', 'N/A', 'N/A']	6	0	14	21	11	288	0	960	284
dulwich.porcelain.checkout	dulwich.porcelain	4	['N/A', 'N/A', 'N/A', 'N/A']	10	0	12	15	9	273	2	919	253
dulwich.cli.cmd_rebase.run	dulwich.cli	2	['N/A', 'N/A']	9	0	15	4	5	174	0	586	219
dulwich.object_store.DiskObjectStore._complete_pack	dulwich.object_store	6	['N/A', 'N/A', 'N/A', 'N/A', 'N/A', 'N/A']	9	0	13	3	4	144	2	454	207

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

Functions statically reachable by fuzzers

508 / 1943

Cyclomatic complexity statically reachable by fuzzers

1904 / 6911

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/dulwich/fuzzing/fuzz-targets/fuzz_bundle.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=['...dulwich.fuzzing.fuzz-targets.fuzz_bundle.TestOneInput', 'dulwich.file.GitFile', 'dulwich.bundle._read_bundle', 'dulwich.file._GitFile.__init__']

/src/dulwich/fuzzing/fuzz-targets/fuzz_configfile.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=['dulwich.config.ConfigFile.__init__']

/src/dulwich/fuzzing/fuzz-targets/fuzz_object_store.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=['...dulwich.fuzzing.fuzz-targets.fuzz_object_store.TestOneInput', 'dulwich.objects.S_ISGITLINK']

/src/dulwich/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=['dulwich.config.StackedConfig.get', 'dulwich.config.StackedConfig.default_backends', 'dulwich.config.ConfigDict.items', 'dulwich.repo.Repo.__init__', 'dulwich.repo.Repo._init_maybe_bare', 'dulwich.repo.Repo.get_named_file', '...dulwich.fuzzing.fuzz-targets.fuzz_repo.TestOneInput']

This section shows analysis of runtime coverage data.

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

Complex functions with low coverage

Func name	Function total lines	Lines covered at runtime	percentage covered	Reached by fuzzers
dulwich.pack.read_zlib_chunks	33	0	0.0%	[]
dulwich.pack.unpack_object	32	0	0.0%	[]
dulwich.pack.PackChunkGenerator._pack_data_chunks	38	0	0.0%	['fuzz_bundle']
dulwich.pack.apply_delta.get_delta_header_size	44	0	0.0%	[]
dulwich.pack.write_pack_index_v3	37	0	0.0%	[]
dulwich.objects.Tag._deserialize	31	0	0.0%	[]
dulwich.objects.parse_commit	45	5	11.11%	['fuzz_bundle', 'fuzz_object_store', 'fuzz_repo', 'fuzz_configfile']
dulwich.objects.Commit.check	32	0	0.0%	[]
repo.refs.read_ref	44	23	52.27%	['fuzz_bundle', 'fuzz_object_store', 'fuzz_repo', 'fuzz_configfile']
dulwich.object_store.DiskObjectStore._complete_pack	31	0	0.0%	[]
dulwich.object_store.DiskObjectStore.write_commit_graph	33	0	0.0%	[]
dulwich.gc.find_reachable_objects	38	0	0.0%	[]
dulwich.gc.garbage_collect	52	0	0.0%	[]
dulwich.gc.maybe_auto_gc	34	2	5.882%	['fuzz_bundle', 'fuzz_object_store', 'fuzz_repo', 'fuzz_configfile']
dulwich.repo.Repo.stage	39	21	53.84%	['fuzz_bundle', 'fuzz_object_store', 'fuzz_repo', 'fuzz_configfile']
dulwich.repo.Repo.clone	40	0	0.0%	[]
dulwich.repo.Repo.get_gitattributes	31	0	0.0%	[]
dulwich.config.ConfigFile._evaluate_hasconfig_condition	34	0	0.0%	[]
dulwich.refs.DiskRefsContainer.set_if_equals	39	0	0.0%	[]
dulwich.refs.DiskRefsContainer.remove_if_equals	34	0	0.0%	[]
dulwich.index._decompress_path_from_stream	47	19	40.42%	['fuzz_bundle', 'fuzz_object_store', 'fuzz_repo', 'fuzz_configfile']
dulwich.index.read_index_dict_with_version	42	18	42.85%	['fuzz_bundle', 'fuzz_object_store', 'fuzz_repo', 'fuzz_configfile']
dulwich.index.update_working_tree	90	0	0.0%	[]
dulwich.diff_tree.walk_trees	50	9	18.0%	['fuzz_bundle', 'fuzz_object_store', 'fuzz_repo', 'fuzz_configfile']
dulwich.patch.parse_patch_message	39	0	0.0%	[]
dulwich.protocol.ReceivableProtocol.read	31	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
	[]	[]
dulwich.reflog	[]	[]
dulwich.cli	[]	[]
dulwich.diff_tree	[]	[]
typing_extensions	[]	[]
dulwich.diff	[]	[]
dulwich.commit_graph	[]	[]
requests	[]	[]
dataclasses	[]	[]
collections	[]	[]
dulwich.contrib.swift	['fuzz_bundle']	[]
optparse	[]	[]
dulwich.bisect	[]	[]
...dulwich.fuzzing.fuzz-targets.fuzz_object_store	['fuzz_object_store']	[]
dulwich.contrib.requests_vendor	[]	[]
os	[]	[]
dulwich.protocol	[]	[]
hashlib	[]	[]
dulwich.line_ending	[]	[]
dulwich.log_utils	[]	[]
ctypes	[]	[]
dulwich.gc	[]	[]
platform	[]	[]
dulwich.bundle	['fuzz_bundle']	[]
dulwich.rebase	[]	[]
itertools	[]	[]
dulwich.pack	['fuzz_bundle']	[]
dulwich.lru_cache	[]	[]
gzip	[]	[]
...dulwich.fuzzing.fuzz-targets.fuzz_bundle	['fuzz_bundle']	[]
nturl2path	[]	[]
urllib3	[]	[]
typing	[]	[]
dulwich.contrib	[]	[]
dulwich.web	[]	[]
dulwich.notes	[]	[]
shlex	[]	[]
dulwich.cloud	[]	[]
pwd	[]	[]
tempfile	[]	[]
dulwich.annotate	[]	[]
dulwich.sparse_patterns	[]	[]
dulwich.contrib.paramiko_vendor	[]	[]
geventhttpclient	[]	[]
tarfile	[]	[]
argparse	[]	[]
ipaddress	[]	[]
	[]	[]
dulwich.filter_branch	[]	[]
binascii	[]	[]
re	[]	[]
dulwich.file	['fuzz_bundle']	[]
dulwich.dumb	[]	[]
paramiko	[]	[]
gpg	[]	[]
dulwich.archive	[]	[]
wsgiref	[]	[]
dulwich.attrs	[]	[]
time	[]	[]
subprocess	[]	[]
win32api	[]	[]
shutil	[]	[]
dulwich.repo	['fuzz_object_store', 'fuzz_repo']	[]
warnings	[]	[]
dulwich.mailmap	[]	[]
...dulwich.fuzzing.fuzz-targets.fuzz_configfile	['fuzz_configfile']	[]
dulwich.lfs	[]	[]
msvcrt	[]	[]
dulwich.object_store	['fuzz_object_store', 'fuzz_repo']	[]
test_utils	[]	[]
replace_me	[]	[]
contextlib	[]	[]
dulwich.objectspec	[]	[]
dulwich.walk	[]	[]
fastimport	[]	[]
urllib	[]	[]
io	[]	[]
dulwich.client	[]	[]
dulwich.__main__	[]	[]
gc	[]	[]
atheris	[]	[]
functools	[]	[]
stat	[]	[]
posixpath	[]	[]
dulwich.index	[]	[]
pathlib	[]	[]
pdb	[]	[]
dulwich.refs	['fuzz_object_store', 'fuzz_repo']	[]
dulwich.objects	['fuzz_object_store', 'fuzz_repo']	[]
dulwich	[]	[]
json	[]	[]
select	[]	[]
merge3	[]	[]
cdifflib	[]	[]
dulwich.errors	[]	[]
dulwich.reftable	['fuzz_repo']	[]
dulwich.filters	[]	[]
dulwich.merge	[]	[]
datetime	[]	[]
glob	[]	[]
dulwich.config	['fuzz_configfile', 'fuzz_object_store', 'fuzz_repo']	[]
difflib	[]	[]
dulwich.server	[]	[]
unicodedata	[]	[]
mmap	[]	[]
dulwich.submodule	[]	[]
signal	[]	[]
dulwich.fastexport	[]	[]
dulwich.cloud.gcs	[]	[]
struct	[]	[]
socket	[]	[]
winreg	[]	[]
configparser	[]	[]
dulwich.ignore	[]	[]
fnmatch	[]	[]
zlib	[]	[]
logging	[]	[]
dulwich.credentials	[]	[]
dulwich.patch	['fuzz_object_store']	[]
dulwich.contrib.diffstat	[]	[]
dulwich.graph	[]	[]
sys	[]	[]
dulwich.porcelain	[]	[]
gevent	[]	[]
copy	[]	[]
random	[]	[]
dulwich.contrib.release_robot	[]	[]
dulwich.hooks	['fuzz_repo']	[]
dulwich.stash	[]	[]
...dulwich.fuzzing.fuzz-targets.fuzz_repo	['fuzz_repo']	[]
socketserver	[]	[]
heapq	[]	[]
dulwich.greenthreads	[]	[]

Directories in report

Directory