High level conclusions

Fuzzers reach 78.25% of cyclomatic complexity.

Fuzzers reach 68.69% of all functions.

Fuzzer fuzz-htsparse is blocked:

The runtime code coverage of fuzz-htsparse covers 28.13% 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

981 / 1428

Cyclomatic complexity statically reachable by fuzzers

15008 / 19178

Runtime code coverage of functions

492 / 1428

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-filters

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	2.32%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	42	97.6%
All colors	43	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	LLVMFuzzerTestOneInput	call site: 00005	strjoker_bounded

Runtime coverage analysis

Covered functions

11

Functions that are reachable but not covered

6

Reachable functions

17

Percentage of reachable functions covered

64.71%

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
fuzz/fuzz-filters.c	1
fuzz/fuzz.h	1
src/htsfilters.c	8
src/./htslib.h	1

Fuzzer: fuzz-codepage

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	5	15.1%
gold	[1:9]	3	9.09%
yellow	[10:29]	2	6.06%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	23	69.6%
All colors	33	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	22	hts_codepageToUTF8	call site: 00022	log_abort_
1	11	hts_convertStringToUTF8	call site: 00011	strdup

Runtime coverage analysis

Covered functions

12

Functions that are reachable but not covered

9

Reachable functions

21

Percentage of reachable functions covered

57.14%

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
fuzz/fuzz-codepage.c	1
fuzz/fuzz.h	1
src/htscharset.c	10
src/htssafe.h	2

Fuzzer: fuzz-meta

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]	1	4.16%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	23	95.8%
All colors	24	100

Runtime coverage analysis

Covered functions

8

Functions that are reachable but not covered

1

Reachable functions

9

Percentage of reachable functions covered

88.89%

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
fuzz/fuzz-meta.c	1
fuzz/fuzz.h	1
src/htscharset.c	6

Fuzzer: fuzz-url

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	24	38.7%
gold	[1:9]	6	9.67%
yellow	[10:29]	1	1.61%
greenyellow	[30:49]	1	1.61%
lawngreen	50+	30	48.3%
All colors	62	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
5	8	strcpy_safe_	call site: 00008	log_abort_
4	36	jump_protocol_const	call site: 00036	strrchr_limit
3	45	ident_url_absolute	call site: 00045	strncat_safe_
3	54	ident_url_absolute	call site: 00054	strncat_safe_
2	5	ident_url_absolute	call site: 00005	strcpy_safe_
2	41	strrchr_limit	call site: 00041	strchr
1	3	LLVMFuzzerTestOneInput	call site: 00003	strlen
1	22	strncat_safe_	call site: 00022	strfield
1	27	ident_url_absolute	call site: 00027	jump_identification_const
1	29	jump_identification_const	call site: 00029	jump_protocol_const
1	59	ident_url_absolute	call site: 00059	jump_identification_const

Runtime coverage analysis

Covered functions

12

Functions that are reachable but not covered

15

Reachable functions

27

Percentage of reachable functions covered

44.44%

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
fuzz/fuzz-url.c	1
fuzz/fuzz.h	1
src/htslib.c	7
src/./htslib.h	1
src/./htssafe.h	6

Fuzzer: fuzz-charset

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	15.9%
gold	[1:9]	2	4.54%
yellow	[10:29]	1	2.27%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	34	77.2%
All colors	44	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
5	28	hts_convertUTF8StringToUCS4	call site: 00028	log_abort_
1	9	hts_convertStringToUTF8	call site: 00009	strdup
1	11	hts_convertStringCharset	call site: 00011	hts_stringMemCopy

Runtime coverage analysis

Covered functions

14

Functions that are reachable but not covered

13

Reachable functions

27

Percentage of reachable functions covered

51.85%

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
fuzz/fuzz-charset.c	1
fuzz/fuzz.h	1
src/htscharset.c	12
src/./htssafe.h	2
src/htslib.c	1

Fuzzer: fuzz-header

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	102	31.3%
gold	[1:9]	1	0.30%
yellow	[10:29]	4	1.23%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	218	67.0%
All colors	325	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
36	153	treathead	call site: 00153	hts_log_vprint
17	130	treathead	call site: 00130	convert_time_rfc822
5	13	strcpy_safe_	call site: 00013	log_abort_
4	37	treatfirstline	call site: 00037	strcpy_safe_
4	99	treathead	call site: 00099	hts_header_param
4	206	jump_protocol_const	call site: 00206	strrchr_limit
4	233	treathead	call site: 00233	strfield
3	201	jump_protocol_const	call site: 00201	strfield
3	243	treathead	call site: 00243	cookie_add
2	9	treatfirstline	call site: 00009	hts_is_control_free_sized
2	29	infostatuscode	call site: 00029	strcpy_safe_
2	90	treathead	call site: 00090	strcpy_safe_

Runtime coverage analysis

Covered functions

47

Functions that are reachable but not covered

41

Reachable functions

88

Percentage of reachable functions covered

53.41%

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
fuzz/fuzz-header.c	2
fuzz/fuzz.h	1
src/htslib.c	19
src/./htslib.h	3
src/./htssafe.h	11
src/htsurlport.c	9
src/htscodec.c	1
src/htsdate.c	2
src/htscore.c	2
src/./htsthread.h	3
src/htsbauth.c	9

Fuzzer: fuzz-idna

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	14.8%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	40	85.1%
All colors	47	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
5	4	hts_convertStringUTF8ToIDNA	call site: 00004	log_abort_
2	34	punycode_decode	call site: 00034	abortf_

Runtime coverage analysis

Covered functions

11

Functions that are reachable but not covered

9

Reachable functions

20

Percentage of reachable functions covered

55.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.

Function name	source code lines	source lines hit	percentage hit

Files reached

filename	functions hit
fuzz/fuzz-idna.c	1
fuzz/fuzz.h	1
src/htscharset.c	4
src/./htssafe.h	2
src/htslib.c	1
src/punycode.c	6

Fuzzer: fuzz-arc

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	75	25.0%
gold	[1:9]	13	4.34%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	211	70.5%
All colors	299	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
14	180	coucal_add_item_	call site: 00180	coucal_log_stats
7	37	PT_LoadCache	call site: 00037	proxytrack_vprint_log
7	135	coucal_log	call site: 00135	coucal_fail
7	148	coucal_realloc_pool	call site: 00148	coucal_compact_pool
7	271	coucal_delete	call site: 00271	coucal_del_name
4	60	vslprintfbuff	call site: 00060	log_abort_
4	197	coucal_log_stats	call site: 00197	coucal_do_warning
3	131	coucal_dup_name_internal	call site: 00131	coucal_do_crit
3	239	PT_Enumerate	call site: 00239	fprintf
2	143	coucal_dup_name_internal	call site: 00143	coucal_do_crit
2	156	coucal_realloc_pool	call site: 00156	coucal_do_crit
2	205	coucal_write_value	call site: 00205	coucal_do_crit

Runtime coverage analysis

Covered functions

127

Functions that are reachable but not covered

46

Reachable functions

115

Percentage of reachable functions covered

60.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
fuzz/fuzz-arc.c	5
src/coucal/coucal.c	48
src/proxy/store.c	13
src/proxy/proxytrack.h	6
src/htssafe.h	4
src/coucal/murmurhash3.h	4
src/htslib.h	1
src/htsstrings.h	2

Fuzzer: fuzz-cachendx

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	64	25.2%
gold	[1:9]	14	5.53%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	2	0.79%
lawngreen	50+	173	68.3%
All colors	253	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
14	184	coucal_add_item_	call site: 00184	coucal_log_stats
7	139	coucal_log	call site: 00139	coucal_fail
7	152	coucal_realloc_pool	call site: 00152	coucal_compact_pool
7	243	coucal_delete	call site: 00243	coucal_del_name
4	64	vslprintfbuff	call site: 00064	log_abort_
4	201	coucal_log_stats	call site: 00201	coucal_do_warning
3	135	coucal_dup_name_internal	call site: 00135	coucal_do_crit
2	147	coucal_dup_name_internal	call site: 00147	coucal_do_crit
2	160	coucal_realloc_pool	call site: 00160	coucal_do_crit
2	209	coucal_write_value	call site: 00209	coucal_do_crit
2	225	coucal_write_value	call site: 00225	PT_Index_Delete
1	47	proxytrack_vprint_log	call site: 00047	__errno_location

Runtime coverage analysis

Covered functions

124

Functions that are reachable but not covered

45

Reachable functions

109

Percentage of reachable functions covered

58.72%

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
fuzz/fuzz-cachendx.c	5
src/coucal/coucal.c	47
src/proxy/store.c	10
src/proxy/proxytrack.h	6
src/htssafe.h	4
src/coucal/murmurhash3.h	4
src/htslib.h	1

Fuzzer: fuzz-sitemap

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	28	43.0%
gold	[1:9]	0	0.0%
yellow	[10:29]	1	1.53%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	36	55.3%
All colors	65	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
22	37	hts_unescapeEntitiesWithCharsetSpecial	call site: 00037	hts_convertStringFromUTF8Strict
5	27	hts_unescapeEntitiesWithCharsetSpecial	call site: 00027	log_abort_
1	35	hts_isCharsetUTF8	call site: 00035	strcasecmp

Runtime coverage analysis

Covered functions

20

Functions that are reachable but not covered

26

Reachable functions

46

Percentage of reachable functions covered

43.48%

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
fuzz/fuzz-sitemap.c	2
src/htssitemap.c	5
src/htscodec.c	2
src/htszlib.c	1
src/htstools.c	1
src/htsencoding.c	4
src/./htssafe.h	2
src/htslib.c	1
src/./htsentities.h	1
src/htscharset.c	8
src/./htsencoding.h	1
src/./htslib.h	1

Fuzzer: fuzz-entities

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	14	34.1%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	27	65.8%
All colors	41	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
5	5	hts_unescapeEntitiesWithCharsetSpecial	call site: 00005	log_abort_
4	16	hts_unescapeEntitiesWithCharsetSpecial	call site: 00016	hts_convertStringFromUTF8Strict
2	30	hts_convertStringCharset	call site: 00030	realloc
1	24	hts_convertStringFromUTF8	call site: 00024	strdup
1	26	hts_convertStringCharset	call site: 00026	hts_stringMemCopy
1	36	hts_unescapeEntitiesWithCharsetSpecial	call site: 00036	snprintf

Runtime coverage analysis

Covered functions

15

Functions that are reachable but not covered

16

Reachable functions

31

Percentage of reachable functions covered

48.39%

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
fuzz/fuzz-entities.c	1
fuzz/fuzz.h	1
src/htsencoding.c	4
src/./htssafe.h	2
src/htslib.c	1
src/./htsentities.h	1
src/htscharset.c	8
src/./htsencoding.h	1

Fuzzer: fuzz-unescape

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	31	59.6%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	21	40.3%
All colors	52	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
22	26	hts_unescapeEntitiesWithCharsetSpecial	call site: 00026	hts_convertStringFromUTF8Strict
5	3	unescape_http	call site: 00003	log_abort_
2	16	LLVMFuzzerTestOneInput	call site: 00016	hts_unescapeEntities
1	24	hts_isCharsetUTF8	call site: 00024	strcasecmp
1	50	hts_unescapeEntitiesWithCharsetSpecial	call site: 00050	abortf_

Runtime coverage analysis

Covered functions

14

Functions that are reachable but not covered

21

Reachable functions

35

Percentage of reachable functions covered

40.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.

Function name	source code lines	source lines hit	percentage hit

Files reached

filename	functions hit
fuzz/fuzz-unescape.c	1
fuzz/fuzz.h	1
src/htslib.c	4
src/./htssafe.h	2
src/./htsencoding.h	2
src/htsencoding.c	4
src/./htsentities.h	1
src/htscharset.c	8

Fuzzer: fuzz-singlefile

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	312	42.5%
gold	[1:9]	147	20.0%
yellow	[10:29]	11	1.50%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	263	35.8%
All colors	733	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
24	421	fspc_count	call site: 00421	fspc
23	535	hts_unescapeEntitiesWithCharsetSpecial	call site: 00535	hts_convertStringFromUTF8Strict
21	194	coucal_add_item_	call site: 00194	coucal_log_stats
20	712	sf_inline	call site: 00712	sf_append_escaped
16	234	coucal_write_value	call site: 00234	psl_install
15	6	hts_init	call site: 00006	hts_debug_log_print
13	615	ishtml	call site: 00615	ishtml_ext
11	145	coucal_dup_name_internal	call site: 00145	coucal_do_crit
11	354	openFunctionLib	call site: 00354	hts_debug_log_print
10	409	hts_random_bytes	call site: 00409	hts_log_print
7	32	hts_mptcp_probe	call site: 00032	hts_mptcp_kernel_recovers
7	42	hts_psl_init_from	call site: 00042	coucal_new

Runtime coverage analysis

Covered functions

121

Functions that are reachable but not covered

101

Reachable functions

222

Percentage of reachable functions covered

54.5%

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
fuzz/fuzz-singlefile.c	8
src/htslib.c	30
src/./htssafe.h	8
src/coucal/coucal.c	45
src/htsthread.c	2
src/htspsl.c	6
src/htscharset.c	10
src/punycode.c	4
src/coucal/murmurhash3.h	4
src/htsmodules.c	4
src/htsmd5.c	1
src/md5.c	5
src/./htsstrings.h	1
src/./htsthread.h	3
src/htsstrings.h	1
src/htssinglefile.c	21
src/htsrandom.c	1
src/htscore.c	2
src/./htslib.h	3
src/htsencoding.c	4
src/./htsentities.h	1
src/./htsencoding.h	2
src/htsconcat.c	4
src/htscache.c	1
src/./htsio.h	1

Fuzzer: fuzz-htsparse

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	4899	81.3%
gold	[1:9]	26	0.43%
yellow	[10:29]	11	0.18%
greenyellow	[30:49]	1	0.01%
lawngreen	50+	1085	18.0%
All colors	6022	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
1342	3181	back_delete	call site: 03181	back_cleanup_background
784	4525	engine_stats	call site: 04525	url_savename
610	2553	back_finalize	call site: 02553	cache_mayadd
302	1931	url_savename	call site: 01931	cache_read_including_broken
175	1726	hts_acceptlink_	call site: 01726	hts_host_same_alias
152	5360	htsparse	call site: 05360	hts_mirror_process_user_interaction
117	2246	back_clear_entry	call site: 02246	resolve_extension
93	1051	hts_gmtime	call site: 01051	usercommand
91	2364	back_status	call site: 02364	hts_wait_available_socket
86	5515	hts_addurl_take	call site: 05515	hts_wait_delayed
82	5678	htsparse	call site: 05678	verif_backblue
72	718	htsparse	call site: 00718	index_keyword

Runtime coverage analysis

Covered functions

299

Functions that are reachable but not covered

746

Reachable functions

1038

Percentage of reachable functions covered

28.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.

Function name	source code lines	source lines hit	percentage hit

Files reached

filename	functions hit
fuzz/fuzz-htsparse.c	1
src/htslib.c	172
src/./htssafe.h	25
src/coucal/coucal.c	62
src/htsthread.c	10
src/htspsl.c	11
src/htscharset.c	21
src/punycode.c	6
src/coucal/murmurhash3.h	4
src/htsmodules.c	4
src/htsmd5.c	1
src/md5.c	5
src/./htsstrings.h	1
src/./htsthread.h	6
src/htscore.c	71
src/htshash.c	22
src/./htslib.h	13
src/htsurlport.c	14
src/htsfilters.c	8
src/htsescape.c	2
src/htsback.c	101
src/./htsarena.h	5
src/htssafe.h	6
src/htsparse.c	27
src/htssinglefile.c	7
src/htsrandom.c	1
src/htstools.c	29
src/htsindex.c	2
src/htsconcat.c	7
src/htschanges.c	10
src/./htsio.h	2
src/htsencoding.c	6
src/./htsentities.h	1
src/./htsencoding.h	2
src/htswizard.c	18
src/htsrobots.c	4
src/htsname.c	26
src/htscache.c	16
src/minizip/unzip.c	13
src/minizip/ioapi.c	3
src/htswarc.c	45
src/htssniff.c	8
src/./htsback.h	1
src/htscodec.c	7
src/htszlib.c	3
src/./htsbasenet.h	1
src/htsdate.c	2
src/./htsname.h	1
src/./htscore.h	1
src/minizip/zip.c	15
src/minizip/crypt.h	4
src/htsnet.c	1
src/./htsnet.h	4
src/htscrashtest.c	4
src/htsproxy.c	11
src/htsfetch.c	22
src/htslines.c	3
src/htsbauth.c	12
src/htsftp.c	28
src/htssitemap.c	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
httpmirror	/src/httrack/src/htscore.c	3	['N/A', 'N/A', 'N/A']	26	0	10988	1783	566	1202	0	16749	2086
PT_ReadCache__Old	/src/httrack/src/proxy/store.c	3	['N/A', 'N/A', 'int']	9	0	32	3	2	84	0	377	183
hts_buildtopindex	/src/httrack/src/htstools.c	3	['N/A', 'N/A', 'N/A']	16	0	1923	353	90	155	0	982	166
PT_LoadCache__Arc	/src/httrack/src/proxy/store.c	2	['N/A', 'N/A']	11	0	390	62	23	82	0	398	144
PT_ReadCache__New	/src/httrack/src/proxy/store.c	3	['N/A', 'N/A', 'int']	9	0	32	3	2	91	0	528	118
copy_htsopt	/src/httrack/src/htscore.c	2	['N/A', 'N/A']	2	0	2304	345	96	6	0	108	96
PT_SaveCache__New	/src/httrack/src/proxy/store.c	2	['N/A', 'N/A']	8	0	54	9	4	87	0	578	68
PT_ReadCache__Arc	/src/httrack/src/proxy/store.c	3	['N/A', 'N/A', 'int']	9	0	32	3	2	59	0	228	68
PT_Index_HTML_BuildRootInfo	/src/httrack/src/proxy/store.c	1	['N/A']	6	0	1460	246	59	17	0	96	59
hts_getcategories	/src/httrack/src/htstools.c	2	['N/A', 'int']	11	0	1208	222	58	93	0	482	58

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

Functions statically reachable by fuzzers

1187 / 1428

Cyclomatic complexity statically reachable by fuzzers

18032 / 19178

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.

fuzz/fuzz-filters.c

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=['LLVMFuzzerTestOneInput']

fuzz/fuzz-codepage.c

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=['hts_codepageToUTF8', 'hts_convertStringToUTF8']

fuzz/fuzz-meta.c

Dictionary

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

fuzz/fuzz-url.c

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=['strcpy_safe_', 'jump_protocol_const', 'ident_url_absolute', 'strrchr_limit', 'LLVMFuzzerTestOneInput', 'strncat_safe_', 'jump_identification_const']

fuzz/fuzz-charset.c

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=['hts_convertUTF8StringToUCS4', 'hts_convertStringToUTF8', 'hts_convertStringCharset']

fuzz/fuzz-header.c

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=['treathead', 'strcpy_safe_', 'treatfirstline', 'jump_protocol_const']

fuzz/fuzz-idna.c

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=['hts_convertStringUTF8ToIDNA', 'punycode_decode']

fuzz/fuzz-arc.c

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=['coucal_add_item_', 'PT_LoadCache', 'coucal_log', 'coucal_realloc_pool', 'coucal_delete', 'vslprintfbuff', 'coucal_log_stats', 'coucal_dup_name_internal', 'PT_Enumerate']

fuzz/fuzz-cachendx.c

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=['coucal_add_item_', 'coucal_log', 'coucal_realloc_pool', 'coucal_delete', 'vslprintfbuff', 'coucal_log_stats', 'coucal_dup_name_internal', 'coucal_write_value']

fuzz/fuzz-sitemap.c

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=['hts_unescapeEntitiesWithCharsetSpecial', 'hts_isCharsetUTF8']

fuzz/fuzz-entities.c

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=['hts_unescapeEntitiesWithCharsetSpecial', 'hts_convertStringCharset', 'hts_convertStringFromUTF8']

fuzz/fuzz-unescape.c

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=['hts_unescapeEntitiesWithCharsetSpecial', 'unescape_http', 'LLVMFuzzerTestOneInput', 'hts_isCharsetUTF8']

fuzz/fuzz-singlefile.c

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=['fspc_count', 'hts_unescapeEntitiesWithCharsetSpecial', 'coucal_add_item_', 'sf_inline', 'coucal_write_value', 'hts_init', 'ishtml', 'coucal_dup_name_internal', 'openFunctionLib', 'hts_random_bytes']

fuzz/fuzz-htsparse.c

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=['back_delete', 'engine_stats', 'back_finalize', 'url_savename', 'hts_acceptlink_', 'htsparse', 'back_clear_entry', 'hts_gmtime', 'back_status', 'hts_addurl_take']

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
hts_log_vprint	52	22	42.30%	['fuzz-header', 'fuzz-htsparse', 'fuzz-singlefile']
coucal_add_item_	131	64	48.85%	['fuzz-cachendx', 'fuzz-htsparse', 'fuzz-singlefile', 'fuzz-arc']
MD5Update	31	16	51.61%	['fuzz-cachendx', 'fuzz-htsparse', 'fuzz-singlefile', 'fuzz-arc']
plug_wrapper	45	11	24.44%	['fuzz-htsparse', 'fuzz-singlefile']
hts_random_bytes	36	17	47.22%	['fuzz-htsparse', 'fuzz-singlefile']
back_finalize	378	21	5.555%	['fuzz-htsparse']
hts_changes_notify	53	11	20.75%	['fuzz-htsparse']
hts_changes_html	36	11	30.55%	['fuzz-htsparse']
hts_finish_makeindex	33	6	18.18%	['fuzz-htsparse']
hts_finish_html_file	42	16	38.09%	['fuzz-htsparse']
engine_stats	32	8	25.0%	['fuzz-htsparse']
hash_read	37	19	51.35%	['fuzz-htsparse']
hts_query_strip_keys	36	8	22.22%	['fuzz-htsparse']
hts_host_alias_resolve	76	9	11.84%	['fuzz-htsparse']
url_savename	1034	75	7.253%	['fuzz-htsparse']
hts_acceptlink_	435	30	6.896%	['fuzz-htsparse']

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
	[]	[]
/src/httrack/fuzz/fuzz-entities.c	['fuzz-entities']	['fuzz-entities']
/src/httrack/fuzz/fuzz-codepage.c	['fuzz-codepage']	['fuzz-codepage']
/src/httrack/src/punycode.c	['fuzz-idna', 'fuzz-singlefile', 'fuzz-htsparse']	['fuzz-idna', 'fuzz-singlefile', 'fuzz-htsparse']
/src/httrack/src/htsproxy.c	['fuzz-htsparse']	[]
/src/httrack/fuzz/fuzz-meta.c	['fuzz-meta']	['fuzz-meta']
/src/httrack/src/./htsencoding.h	['fuzz-sitemap', 'fuzz-entities', 'fuzz-unescape', 'fuzz-singlefile', 'fuzz-htsparse']	[]
/src/httrack/src/htswizard.c	['fuzz-htsparse']	['fuzz-htsparse']
/src/httrack/src/htssitemap.c	['fuzz-sitemap', 'fuzz-htsparse']	['fuzz-sitemap', 'fuzz-htsparse']
/src/httrack/fuzz/fuzz-header.c	['fuzz-header']	['fuzz-header']
/src/httrack/src/minizip/crypt.h	['fuzz-htsparse']	[]
/src/httrack/src/proxy/proxytrack.h	['fuzz-arc', 'fuzz-cachendx']	['fuzz-arc', 'fuzz-cachendx']
/src/httrack/src/./htsarena.h	['fuzz-htsparse']	[]
/src/httrack/src/./htslib.h	['fuzz-filters', 'fuzz-url', 'fuzz-header', 'fuzz-sitemap', 'fuzz-singlefile', 'fuzz-htsparse']	[]
/src/httrack/src/htsurlport.c	['fuzz-header', 'fuzz-htsparse']	['fuzz-header', 'fuzz-htsparse']
/src/httrack/src/./htsback.h	['fuzz-htsparse']	[]
/src/httrack/src/htscodec.c	['fuzz-header', 'fuzz-sitemap', 'fuzz-htsparse']	['fuzz-header', 'fuzz-sitemap']
/src/httrack/src/htsthread.c	['fuzz-singlefile', 'fuzz-htsparse']	['fuzz-singlefile', 'fuzz-htsparse']
/src/httrack/src/htsname.c	['fuzz-htsparse']	['fuzz-htsparse']
/src/httrack/fuzz/fuzz-htsparse.c	['fuzz-htsparse']	['fuzz-htsparse']
/src/httrack/src/htsfetch.c	['fuzz-htsparse']	['fuzz-htsparse']
/src/httrack/src/htsencoding.c	['fuzz-sitemap', 'fuzz-entities', 'fuzz-unescape', 'fuzz-singlefile', 'fuzz-htsparse']	['fuzz-sitemap', 'fuzz-entities', 'fuzz-unescape', 'fuzz-singlefile', 'fuzz-htsparse']
/src/httrack/fuzz/fuzz-cachendx.c	['fuzz-cachendx']	['fuzz-cachendx']
/src/httrack/src/htscharset.c	['fuzz-codepage', 'fuzz-meta', 'fuzz-charset', 'fuzz-idna', 'fuzz-sitemap', 'fuzz-entities', 'fuzz-unescape', 'fuzz-singlefile', 'fuzz-htsparse']	['fuzz-codepage', 'fuzz-meta', 'fuzz-charset', 'fuzz-idna', 'fuzz-sitemap', 'fuzz-entities', 'fuzz-unescape', 'fuzz-singlefile', 'fuzz-htsparse']
/src/httrack/src/htsmd5.c	['fuzz-singlefile', 'fuzz-htsparse']	['fuzz-singlefile', 'fuzz-htsparse']
/src/httrack/src/htssniff.c	['fuzz-htsparse']	[]
/src/httrack/src/htslines.c	['fuzz-htsparse']	[]
/src/httrack/src/./htsbasenet.h	['fuzz-htsparse']	[]
/src/httrack/src/htsftp.c	['fuzz-htsparse']	['fuzz-htsparse']
/src/httrack/fuzz/fuzz-filters.c	['fuzz-filters']	['fuzz-filters']
/src/httrack/src/./htsname.h	['fuzz-htsparse']	[]
/src/httrack/src/htsrandom.c	['fuzz-singlefile', 'fuzz-htsparse']	['fuzz-singlefile']
/src/httrack/src/md5.c	['fuzz-singlefile', 'fuzz-htsparse']	['fuzz-singlefile', 'fuzz-htsparse']
/src/httrack/src/htsdate.c	['fuzz-header', 'fuzz-htsparse']	[]
/src/httrack/src/htsindex.c	['fuzz-htsparse']	[]
/src/httrack/src/htssafe.h	['fuzz-codepage', 'fuzz-arc', 'fuzz-cachendx', 'fuzz-htsparse']	[]
/src/httrack/src/proxy/store.c	['fuzz-arc', 'fuzz-cachendx']	['fuzz-arc', 'fuzz-cachendx']
/src/httrack/src/htsparse.c	['fuzz-htsparse']	['fuzz-htsparse']
/src/httrack/src/./htsstrings.h	['fuzz-singlefile', 'fuzz-htsparse']	['fuzz-arc']
/src/httrack/src/htsconcat.c	['fuzz-singlefile', 'fuzz-htsparse']	['fuzz-singlefile', 'fuzz-htsparse']
/src/httrack/src/htspsl.c	['fuzz-singlefile', 'fuzz-htsparse']	['fuzz-singlefile', 'fuzz-htsparse']
/src/httrack/src/htsescape.c	['fuzz-htsparse']	['fuzz-htsparse']
/src/httrack/src/minizip/ioapi.c	['fuzz-htsparse']	[]
/src/httrack/src/htsmodules.c	['fuzz-singlefile', 'fuzz-htsparse']	['fuzz-singlefile', 'fuzz-htsparse']
/src/httrack/fuzz/fuzz.h	['fuzz-filters', 'fuzz-codepage', 'fuzz-meta', 'fuzz-url', 'fuzz-charset', 'fuzz-header', 'fuzz-idna', 'fuzz-entities', 'fuzz-unescape']	['fuzz-filters', 'fuzz-codepage', 'fuzz-meta', 'fuzz-url', 'fuzz-charset', 'fuzz-header', 'fuzz-idna', 'fuzz-entities', 'fuzz-unescape']
/src/httrack/src/htsbauth.c	['fuzz-header', 'fuzz-htsparse']	['fuzz-header']
/src/httrack/src/htssinglefile.c	['fuzz-singlefile', 'fuzz-htsparse']	['fuzz-singlefile', 'fuzz-htsparse']
/src/httrack/fuzz/fuzz-unescape.c	['fuzz-unescape']	['fuzz-unescape']
/src/httrack/src/./htsthread.h	['fuzz-header', 'fuzz-singlefile', 'fuzz-htsparse']	[]
/src/httrack/src/minizip/mztools.c	[]	[]
/src/httrack/fuzz/fuzz-singlefile.c	['fuzz-singlefile']	['fuzz-singlefile']
/src/httrack/src/coucal/murmurhash3.h	['fuzz-arc', 'fuzz-cachendx', 'fuzz-singlefile', 'fuzz-htsparse']	['fuzz-arc', 'fuzz-cachendx', 'fuzz-singlefile', 'fuzz-htsparse']
/src/httrack/src/htsstrings.h	['fuzz-arc', 'fuzz-singlefile']	['fuzz-arc']
/src/httrack/src/./htsnet.h	['fuzz-htsparse']	[]
/src/httrack/fuzz/fuzz-idna.c	['fuzz-idna']	['fuzz-idna']
/src/httrack/src/htschanges.c	['fuzz-htsparse']	['fuzz-htsparse']
/src/httrack/fuzz/fuzz-sitemap.c	['fuzz-sitemap']	['fuzz-sitemap']
/src/httrack/src/htsback.c	['fuzz-htsparse']	['fuzz-htsparse']
/src/httrack/src/htsfilters.c	['fuzz-filters', 'fuzz-htsparse']	['fuzz-filters']
/src/httrack/src/./htssafe.h	['fuzz-url', 'fuzz-charset', 'fuzz-header', 'fuzz-idna', 'fuzz-sitemap', 'fuzz-entities', 'fuzz-unescape', 'fuzz-singlefile', 'fuzz-htsparse']	[]
/src/httrack/src/./htsentities.h	['fuzz-sitemap', 'fuzz-entities', 'fuzz-unescape', 'fuzz-singlefile', 'fuzz-htsparse']	[]
/src/httrack/fuzz/fuzz-arc.c	['fuzz-arc']	['fuzz-arc']
/src/httrack/src/htsnet.c	['fuzz-htsparse']	[]
/src/httrack/src/htsrobots.c	['fuzz-htsparse']	['fuzz-htsparse']
/src/httrack/src/htscore.c	['fuzz-header', 'fuzz-singlefile', 'fuzz-htsparse']	['fuzz-singlefile', 'fuzz-htsparse']
/src/httrack/src/minizip/zip.c	['fuzz-htsparse']	[]
/src/httrack/src/htszlib.c	['fuzz-sitemap', 'fuzz-htsparse']	['fuzz-sitemap']
/src/httrack/src/htstools.c	['fuzz-sitemap', 'fuzz-htsparse']	['fuzz-sitemap', 'fuzz-htsparse']
/src/httrack/src/htslib.c	['fuzz-url', 'fuzz-charset', 'fuzz-header', 'fuzz-idna', 'fuzz-sitemap', 'fuzz-entities', 'fuzz-unescape', 'fuzz-singlefile', 'fuzz-htsparse']	['fuzz-url', 'fuzz-header', 'fuzz-unescape', 'fuzz-singlefile', 'fuzz-htsparse']
/src/httrack/src/htshash.c	['fuzz-htsparse']	['fuzz-htsparse']
/src/httrack/src/minizip/unzip.c	['fuzz-htsparse']	[]
/src/httrack/src/htscache.c	['fuzz-singlefile', 'fuzz-htsparse']	['fuzz-singlefile']
/src/httrack/fuzz/fuzz-charset.c	['fuzz-charset']	['fuzz-charset']
/src/httrack/src/htscrashtest.c	['fuzz-htsparse']	[]
/src/httrack/src/htscmdline.c	[]	[]
/src/httrack/src/proxy/proxystrings.h	[]	[]
/src/httrack/fuzz/fuzz-url.c	['fuzz-url']	['fuzz-url']
/src/httrack/src/./htsio.h	['fuzz-singlefile', 'fuzz-htsparse']	[]
/src/httrack/src/./htscore.h	['fuzz-htsparse']	[]
/src/httrack/src/htswarc.c	['fuzz-htsparse']	['fuzz-htsparse']
/src/httrack/src/coucal/coucal.c	['fuzz-arc', 'fuzz-cachendx', 'fuzz-singlefile', 'fuzz-htsparse']	['fuzz-arc', 'fuzz-cachendx', 'fuzz-singlefile', 'fuzz-htsparse']

Directories in report

Directory
/src/httrack/src/coucal/
/src/httrack/src/proxy/
/src/httrack/src/minizip/
/src/httrack/fuzz/
/src/httrack/src/
/src/httrack/src/./