High level conclusions

Fuzzers reach 0.0% of cyclomatic complexity.

Fuzzers reach 0.299% of all functions.

Reachability and coverage overview

Functions statically reachable by fuzzers

1 / 334

Cyclomatic complexity statically reachable by fuzzers

0 / 466

Runtime code coverage of functions

98 / 334

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_any_spec

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	84.2%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	2	0.30%
lawngreen	50+	102	15.4%
All colors	659	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
315	108	Ascii::next	call site: 00108	encoding_update
105	532	gen::rev_spec	call site: 00532	gen_spec_base
34	425	cmd::execute	call site: 00425	DynEncoding::specification
30	61	Specification::encoding	call site: 00061	load_preset
27	19	string	call site: 00019	Encoding::decode_len
20	638	gen::bytes	call site: 00638	gen_spec_base
8	94	Ascii::rev	call site: 00094	parse_map
5	2	cmd::execute	call site: 00002
3	15	bytes	call site: 00015
2	104	Ascii::next	call site: 00104	Ascii::next
2	479	Encoding::is_canonical	call site: 00479
2	482	Encoding::is_canonical	call site: 00482

Runtime coverage analysis

Covered functions

45

Functions that are reachable but not covered

1

Reachable functions

2

Percentage of reachable functions covered

50.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
lib/fuzz/fuzz_targets/fuzz_any_spec.rs	2
lib/fuzz/src/cmd.rs	37
lib/src/lib.rs	23
lib/fuzz/src/gen.rs	24
lib/macro/internal/src/lib.rs	21
lib/fuzz/src/spec.rs	8
lib/tests/lib.rs	15
www/src/utf8.rs	8
www/src/lib.rs	62
bin/src/main.rs	11
www/src/state.rs	53
lib/fuzz/examples/analyze.rs	2
lib/v3/src/lib.rs	16
nostd/src/main.rs	4

Fuzzer: spec_spec_base

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	622	94.3%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	37	5.61%
All colors	659	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
352	108	Ascii::next	call site: 00108	encoding_update
114	543	gen_spec_base	call site: 00543	gen_spec_base
51	8	BothOutput::default	call site: 00008	Specification::encoding
44	489	Ascii::new	call site: 00489	gen_spec_base
41	61	Specification::encoding	call site: 00061	load_preset
5	2	cmd::execute	call site: 00002
5	482	Encoding::is_canonical	call site: 00482
4	536	gen_spec_base	call site: 00536	debug
2	104	Ascii::next	call site: 00104	Ascii::next
2	479	Encoding::is_canonical	call site: 00479
1	0	EP	call site: 00000
1	534	gen_spec_base	call site: 00534

Runtime coverage analysis

Covered functions

36

Functions that are reachable but not covered

1

Reachable functions

2

Percentage of reachable functions covered

50.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
lib/fuzz/fuzz_targets/spec_spec_base.rs	2
lib/fuzz/src/cmd.rs	37
lib/src/lib.rs	23
lib/fuzz/src/gen.rs	24
lib/macro/internal/src/lib.rs	21
lib/fuzz/src/spec.rs	8
lib/tests/lib.rs	15
www/src/utf8.rs	8
www/src/lib.rs	62
bin/src/main.rs	11
www/src/state.rs	53
lib/fuzz/examples/analyze.rs	2
lib/v3/src/lib.rs	16
nostd/src/main.rs	4

Fuzzer: impl_new_encoder

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	605	91.8%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	54	8.19%
All colors	659	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
352	108	Ascii::next	call site: 00108	encoding_update
84	543	gen_spec_base	call site: 00543	gen_spec_base
44	15	bytes	call site: 00015	Specification::encoding
44	489	Ascii::new	call site: 00489	gen_spec_base
41	61	Specification::encoding	call site: 00061	load_preset
7	651	cmd::execute	call site: 00651	gen_spec_base
6	8	BothOutput::default	call site: 00008	string
5	2	cmd::execute	call site: 00002
5	482	Encoding::is_canonical	call site: 00482
5	641	cmd::execute	call site: 00641
4	536	gen_spec_base	call site: 00536	debug
2	104	Ascii::next	call site: 00104	Ascii::next

Runtime coverage analysis

Covered functions

218

Functions that are reachable but not covered

1

Reachable functions

2

Percentage of reachable functions covered

50.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
lib/fuzz/fuzz_targets/impl_new_encoder.rs	2
lib/fuzz/src/cmd.rs	37
lib/src/lib.rs	23
lib/fuzz/src/gen.rs	24
lib/macro/internal/src/lib.rs	21
lib/fuzz/src/spec.rs	8
lib/tests/lib.rs	15
www/src/utf8.rs	8
www/src/lib.rs	62
bin/src/main.rs	11
www/src/state.rs	53
lib/fuzz/examples/analyze.rs	2
lib/v3/src/lib.rs	16
nostd/src/main.rs	4

Fuzzer: impl_encode_write_buffer

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	615	93.3%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	44	6.67%
All colors	659	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
352	108	Ascii::next	call site: 00108	encoding_update
51	8	BothOutput::default	call site: 00008	Specification::encoding
47	543	gen_spec_base	call site: 00543	gen_spec_base
44	489	Ascii::new	call site: 00489	gen_spec_base
41	61	Specification::encoding	call site: 00061	load_preset
30	596	cmd::execute	call site: 00596	Encoding::encode_write_buffer_uninit
22	636	gen::nat	call site: 00636	gen_spec_base
7	627	cmd::execute	call site: 00627	gen_spec_base
5	2	cmd::execute	call site: 00002
5	482	Encoding::is_canonical	call site: 00482
4	536	gen_spec_base	call site: 00536	debug
2	104	Ascii::next	call site: 00104	Ascii::next

Runtime coverage analysis

Covered functions

212

Functions that are reachable but not covered

1

Reachable functions

2

Percentage of reachable functions covered

50.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
lib/fuzz/fuzz_targets/impl_encode_write_buffer.rs	2
lib/fuzz/src/cmd.rs	37
lib/src/lib.rs	23
lib/fuzz/src/gen.rs	24
lib/macro/internal/src/lib.rs	21
lib/fuzz/src/spec.rs	8
lib/tests/lib.rs	15
www/src/utf8.rs	8
www/src/lib.rs	62
bin/src/main.rs	11
www/src/state.rs	53
lib/fuzz/examples/analyze.rs	2
lib/v3/src/lib.rs	16
nostd/src/main.rs	4

Fuzzer: impl_encode_mut_str

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	603	91.5%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	56	8.49%
All colors	659	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
90	568	cmd::execute	call site: 00568	gen_spec_base
84	308	encode	call site: 00308	load_preset
67	239	Vec::encode	call site: 00239	text_update
67	393	dec	call site: 00393	load_preset
59	178	range::encode	call site: 00178	load_preset
58	113	bits_value	call site: 00113	encoding_update
51	8	BothOutput::default	call site: 00008	Specification::encoding
44	489	Ascii::new	call site: 00489	gen_spec_base
24	543	gen_spec_base	call site: 00543	gen_spec_base
18	61	Specification::encoding	call site: 00061	load_preset
5	2	cmd::execute	call site: 00002
5	97	bits_value	call site: 00097	Ascii::next

Runtime coverage analysis

Covered functions

217

Functions that are reachable but not covered

1

Reachable functions

2

Percentage of reachable functions covered

50.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
lib/fuzz/fuzz_targets/impl_encode_mut_str.rs	2
lib/fuzz/src/cmd.rs	37
lib/src/lib.rs	23
lib/fuzz/src/gen.rs	24
lib/macro/internal/src/lib.rs	21
lib/fuzz/src/spec.rs	8
lib/tests/lib.rs	15
www/src/utf8.rs	8
www/src/lib.rs	62
bin/src/main.rs	11
www/src/state.rs	53
lib/fuzz/examples/analyze.rs	2
lib/v3/src/lib.rs	16
nostd/src/main.rs	4

Fuzzer: impl_encode_append

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	601	91.1%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	58	8.80%
All colors	659	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
87	571	cmd::execute	call site: 00571	gen_spec_base
84	308	encode	call site: 00308	load_preset
67	239	Vec::encode	call site: 00239	text_update
67	393	dec	call site: 00393	load_preset
59	178	range::encode	call site: 00178	load_preset
58	113	bits_value	call site: 00113	encoding_update
51	8	BothOutput::default	call site: 00008	Specification::encoding
44	489	Ascii::new	call site: 00489	gen_spec_base
25	543	gen_spec_base	call site: 00543	gen_spec_base
18	61	Specification::encoding	call site: 00061	load_preset
5	2	cmd::execute	call site: 00002
5	97	bits_value	call site: 00097	Ascii::next

Runtime coverage analysis

Covered functions

217

Functions that are reachable but not covered

1

Reachable functions

2

Percentage of reachable functions covered

50.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
lib/fuzz/fuzz_targets/impl_encode_append.rs	2
lib/fuzz/src/cmd.rs	37
lib/src/lib.rs	23
lib/fuzz/src/gen.rs	24
lib/macro/internal/src/lib.rs	21
lib/fuzz/src/spec.rs	8
lib/tests/lib.rs	15
www/src/utf8.rs	8
www/src/lib.rs	62
bin/src/main.rs	11
www/src/state.rs	53
lib/fuzz/examples/analyze.rs	2
lib/v3/src/lib.rs	16
nostd/src/main.rs	4

Fuzzer: spec_decode_encode

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	618	93.7%
gold	[1:9]	0	0.0%
yellow	[10:29]	1	0.15%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	40	6.06%
All colors	659	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
352	108	Ascii::next	call site: 00108	encoding_update
108	543	gen_spec_base	call site: 00543	gen_spec_base
51	8	BothOutput::default	call site: 00008	Specification::encoding
44	489	Ascii::new	call site: 00489	gen_spec_base
41	61	Specification::encoding	call site: 00061	load_preset
5	2	cmd::execute	call site: 00002
5	482	Encoding::is_canonical	call site: 00482
4	536	gen_spec_base	call site: 00536	debug
2	104	Ascii::next	call site: 00104	Ascii::next
2	479	Encoding::is_canonical	call site: 00479
2	656	cmd::execute	call site: 00656	gen_spec_base
1	0	EP	call site: 00000

Runtime coverage analysis

Covered functions

293

Functions that are reachable but not covered

1

Reachable functions

2

Percentage of reachable functions covered

50.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
lib/fuzz/fuzz_targets/spec_decode_encode.rs	2
lib/fuzz/src/cmd.rs	37
lib/src/lib.rs	23
lib/fuzz/src/gen.rs	24
lib/macro/internal/src/lib.rs	21
lib/fuzz/src/spec.rs	8
lib/tests/lib.rs	15
www/src/utf8.rs	8
www/src/lib.rs	62
bin/src/main.rs	11
www/src/state.rs	53
lib/fuzz/examples/analyze.rs	2
lib/v3/src/lib.rs	16
nostd/src/main.rs	4

Fuzzer: impl_encode

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	603	91.5%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	56	8.49%
All colors	659	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
115	543	gen_spec_base	call site: 00543	gen_spec_base
84	308	encode	call site: 00308	load_preset
67	239	Vec::encode	call site: 00239	text_update
67	393	dec	call site: 00393	load_preset
59	178	range::encode	call site: 00178	load_preset
58	113	bits_value	call site: 00113	encoding_update
51	8	BothOutput::default	call site: 00008	Specification::encoding
43	489	Ascii::new	call site: 00489
18	61	Specification::encoding	call site: 00061	load_preset
5	2	cmd::execute	call site: 00002
5	97	bits_value	call site: 00097	Ascii::next
5	482	Encoding::is_canonical	call site: 00482

Runtime coverage analysis

Covered functions

217

Functions that are reachable but not covered

1

Reachable functions

2

Percentage of reachable functions covered

50.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
lib/fuzz/fuzz_targets/impl_encode.rs	2
lib/fuzz/src/cmd.rs	37
lib/src/lib.rs	23
lib/fuzz/src/gen.rs	24
lib/macro/internal/src/lib.rs	21
lib/fuzz/src/spec.rs	8
lib/tests/lib.rs	15
www/src/utf8.rs	8
www/src/lib.rs	62
bin/src/main.rs	11
www/src/state.rs	53
lib/fuzz/examples/analyze.rs	2
lib/v3/src/lib.rs	16
nostd/src/main.rs	4

Fuzzer: impl_decode

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	608	92.2%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	51	7.73%
All colors	659	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
279	113	bits_value	call site: 00113	encoding_update
91	567	cmd::execute	call site: 00567	gen_spec_base
67	393	dec	call site: 00393	load_preset
51	8	BothOutput::default	call site: 00008	Specification::encoding
44	489	Ascii::new	call site: 00489	gen_spec_base
20	545	cmd::execute	call site: 00545	Encoding::decode_mut_uninit
18	61	Specification::encoding	call site: 00061	load_preset
5	2	cmd::execute	call site: 00002
5	97	bits_value	call site: 00097	Ascii::next
5	482	Encoding::is_canonical	call site: 00482
4	108	Ascii::next	call site: 00108	Ascii::next
4	536	gen_spec_base	call site: 00536	debug

Runtime coverage analysis

Covered functions

330

Functions that are reachable but not covered

1

Reachable functions

2

Percentage of reachable functions covered

50.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
lib/fuzz/fuzz_targets/impl_decode.rs	2
lib/fuzz/src/cmd.rs	37
lib/src/lib.rs	23
lib/fuzz/src/gen.rs	24
lib/macro/internal/src/lib.rs	21
lib/fuzz/src/spec.rs	8
lib/tests/lib.rs	15
www/src/utf8.rs	8
www/src/lib.rs	62
bin/src/main.rs	11
www/src/state.rs	53
lib/fuzz/examples/analyze.rs	2
lib/v3/src/lib.rs	16
nostd/src/main.rs	4

Fuzzer: spec_encode_decode

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	622	94.3%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	37	5.61%
All colors	659	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
352	108	Ascii::next	call site: 00108	encoding_update
113	543	gen_spec_base	call site: 00543	gen_spec_base
51	8	BothOutput::default	call site: 00008	Specification::encoding
44	489	Ascii::new	call site: 00489	gen_spec_base
41	61	Specification::encoding	call site: 00061	load_preset
5	2	cmd::execute	call site: 00002
5	482	Encoding::is_canonical	call site: 00482
4	536	gen_spec_base	call site: 00536	debug
2	104	Ascii::next	call site: 00104	Ascii::next
2	479	Encoding::is_canonical	call site: 00479
1	0	EP	call site: 00000
1	534	gen_spec_base	call site: 00534

Runtime coverage analysis

Covered functions

413

Functions that are reachable but not covered

1

Reachable functions

2

Percentage of reachable functions covered

50.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
lib/fuzz/fuzz_targets/spec_encode_decode.rs	2
lib/fuzz/src/cmd.rs	37
lib/src/lib.rs	23
lib/fuzz/src/gen.rs	24
lib/macro/internal/src/lib.rs	21
lib/fuzz/src/spec.rs	8
lib/tests/lib.rs	15
www/src/utf8.rs	8
www/src/lib.rs	62
bin/src/main.rs	11
www/src/state.rs	53
lib/fuzz/examples/analyze.rs	2
lib/v3/src/lib.rs	16
nostd/src/main.rs	4

Fuzzer: template

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	531	80.5%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	2	0.30%
lawngreen	50+	126	19.1%
All colors	659	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
84	308	encode	call site: 00308	load_preset
67	239	Vec::encode	call site: 00239	text_update
67	393	dec	call site: 00393	load_preset
64	567	cmd::execute	call site: 00567	gen_spec_base
59	178	range::encode	call site: 00178	load_preset
58	113	bits_value	call site: 00113	encoding_update
27	19	string	call site: 00019	Encoding::decode_len
20	545	cmd::execute	call site: 00545	Encoding::decode_mut_uninit
20	638	gen::bytes	call site: 00638	gen_spec_base
18	61	Specification::encoding	call site: 00061	load_preset
5	2	cmd::execute	call site: 00002
5	97	bits_value	call site: 00097	Ascii::next

Runtime coverage analysis

Covered functions

523

Functions that are reachable but not covered

1

Reachable functions

2

Percentage of reachable functions covered

50.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
lib/fuzz/fuzz_targets/template.rs	2
lib/fuzz/src/cmd.rs	37
lib/src/lib.rs	23
lib/fuzz/src/gen.rs	24
lib/macro/internal/src/lib.rs	21
lib/fuzz/src/spec.rs	8
lib/tests/lib.rs	15
www/src/utf8.rs	8
www/src/lib.rs	62
bin/src/main.rs	11
www/src/state.rs	53
lib/fuzz/examples/analyze.rs	2
lib/v3/src/lib.rs	16
nostd/src/main.rs	4

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

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

Functions statically reachable by fuzzers

1 / 334

Cyclomatic complexity statically reachable by fuzzers

0 / 466

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.

lib/fuzz/fuzz_targets/fuzz_any_spec.rs

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=['Ascii::next', 'gen::rev_spec', 'cmd::execute', 'Specification::encoding', 'string', 'gen::bytes', 'Ascii::rev', 'bytes']

lib/fuzz/fuzz_targets/spec_spec_base.rs

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=['Ascii::next', 'gen_spec_base', 'BothOutput::default', 'Ascii::new', 'Specification::encoding', 'cmd::execute', 'Encoding::is_canonical']

lib/fuzz/fuzz_targets/impl_new_encoder.rs

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=['Ascii::next', 'gen_spec_base', 'bytes', 'Ascii::new', 'Specification::encoding', 'cmd::execute', 'BothOutput::default', 'Encoding::is_canonical']

lib/fuzz/fuzz_targets/impl_encode_write_buffer.rs

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=['Ascii::next', 'BothOutput::default', 'gen_spec_base', 'Ascii::new', 'Specification::encoding', 'cmd::execute', 'gen::nat', 'Encoding::is_canonical']

lib/fuzz/fuzz_targets/impl_encode_mut_str.rs

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=['cmd::execute', 'encode', 'Vec::encode', 'dec', 'range::encode', 'bits_value', 'BothOutput::default', 'Ascii::new', 'gen_spec_base', 'Specification::encoding']

lib/fuzz/fuzz_targets/impl_encode_append.rs

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=['cmd::execute', 'encode', 'Vec::encode', 'dec', 'range::encode', 'bits_value', 'BothOutput::default', 'Ascii::new', 'gen_spec_base', 'Specification::encoding']

lib/fuzz/fuzz_targets/spec_decode_encode.rs

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=['Ascii::next', 'gen_spec_base', 'BothOutput::default', 'Ascii::new', 'Specification::encoding', 'cmd::execute', 'Encoding::is_canonical']

lib/fuzz/fuzz_targets/impl_encode.rs

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=['gen_spec_base', 'encode', 'Vec::encode', 'dec', 'range::encode', 'bits_value', 'BothOutput::default', 'Ascii::new', 'Specification::encoding', 'cmd::execute']

lib/fuzz/fuzz_targets/impl_decode.rs

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=['bits_value', 'cmd::execute', 'dec', 'BothOutput::default', 'Ascii::new', 'Specification::encoding', 'Encoding::is_canonical']

lib/fuzz/fuzz_targets/spec_encode_decode.rs

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=['Ascii::next', 'gen_spec_base', 'BothOutput::default', 'Ascii::new', 'Specification::encoding', 'cmd::execute', 'Encoding::is_canonical']

lib/fuzz/fuzz_targets/template.rs

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=['encode', 'Vec::encode', 'dec', 'cmd::execute', 'range::encode', 'bits_value', 'string', 'gen::bytes', 'Specification::encoding']

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
data_encoding::encode_wrap_mut::data_encoding::N1, data_encoding::Bf, data_encoding::On, data_encoding::On	31	12	38.70%
data_encoding::encode_wrap_mut::data_encoding::N1, data_encoding::Bt, data_encoding::On, data_encoding::On	31	12	38.70%
data_encoding::encode_wrap_mut::data_encoding::N2, data_encoding::Bf, data_encoding::On, data_encoding::On	31	12	38.70%
data_encoding::encode_wrap_mut::data_encoding::N2, data_encoding::Bt, data_encoding::On, data_encoding::On	31	12	38.70%
data_encoding::encode_wrap_mut::data_encoding::N3, data_encoding::Bf, data_encoding::Osu8, data_encoding::On	31	12	38.70%
data_encoding::encode_wrap_mut::data_encoding::N3, data_encoding::Bf, data_encoding::On, data_encoding::On	31	12	38.70%
data_encoding::encode_wrap_mut::data_encoding::N3, data_encoding::Bt, data_encoding::Osu8, data_encoding::On	31	12	38.70%
data_encoding::encode_wrap_mut::data_encoding::N3, data_encoding::Bt, data_encoding::On, data_encoding::On	31	12	38.70%
data_encoding::encode_wrap_mut::data_encoding::N4, data_encoding::Bf, data_encoding::On, data_encoding::On	31	12	38.70%
data_encoding::encode_wrap_mut::data_encoding::N4, data_encoding::Bt, data_encoding::On, data_encoding::On	31	12	38.70%
data_encoding::encode_wrap_mut::data_encoding::N5, data_encoding::Bf, data_encoding::Osu8, data_encoding::On	31	12	38.70%
data_encoding::encode_wrap_mut::data_encoding::N5, data_encoding::Bf, data_encoding::On, data_encoding::On	31	12	38.70%
data_encoding::encode_wrap_mut::data_encoding::N5, data_encoding::Bt, data_encoding::Osu8, data_encoding::On	31	12	38.70%
data_encoding::encode_wrap_mut::data_encoding::N5, data_encoding::Bt, data_encoding::On, data_encoding::On	31	12	38.70%
data_encoding::encode_wrap_mut::data_encoding::N6, data_encoding::Bf, data_encoding::Osu8, data_encoding::On	31	12	38.70%
data_encoding::encode_wrap_mut::data_encoding::N6, data_encoding::Bf, data_encoding::On, data_encoding::On	31	12	38.70%
data_encoding::encode_wrap_mut::data_encoding::N6, data_encoding::Bt, data_encoding::Osu8, data_encoding::On	31	12	38.70%
data_encoding::encode_wrap_mut::data_encoding::N6, data_encoding::Bt, data_encoding::On, data_encoding::On	31	12	38.70%
data_encoding::decode_pad_mut::data_encoding::N1, data_encoding::Bf, data_encoding::Bf	52	6	11.53%
data_encoding::decode_pad_mut::data_encoding::N1, data_encoding::Bt, data_encoding::Bf	52	6	11.53%
data_encoding::decode_pad_mut::data_encoding::N2, data_encoding::Bf, data_encoding::Bf	52	6	11.53%
data_encoding::decode_pad_mut::data_encoding::N2, data_encoding::Bt, data_encoding::Bf	52	6	11.53%
data_encoding::decode_pad_mut::data_encoding::N3, data_encoding::Bf, data_encoding::Bf	52	6	11.53%
data_encoding::decode_pad_mut::data_encoding::N3, data_encoding::Bt, data_encoding::Bf	52	6	11.53%
data_encoding::decode_pad_mut::data_encoding::N4, data_encoding::Bf, data_encoding::Bf	52	6	11.53%
data_encoding::decode_pad_mut::data_encoding::N4, data_encoding::Bt, data_encoding::Bf	52	6	11.53%
data_encoding::decode_pad_mut::data_encoding::N5, data_encoding::Bf, data_encoding::Bf	52	6	11.53%
data_encoding::decode_pad_mut::data_encoding::N5, data_encoding::Bt, data_encoding::Bf	52	6	11.53%
data_encoding::decode_pad_mut::data_encoding::N6, data_encoding::Bf, data_encoding::Bf	52	6	11.53%
data_encoding::decode_pad_mut::data_encoding::N6, data_encoding::Bt, data_encoding::Bf	52	6	11.53%
data_encoding::decode_wrap_mut::data_encoding::N1, data_encoding::Bf, data_encoding::Bf, data_encoding::Bf	44	7	15.90%
data_encoding::decode_wrap_mut::data_encoding::N1, data_encoding::Bt, data_encoding::Bf, data_encoding::Bf	44	7	15.90%
data_encoding::decode_wrap_mut::data_encoding::N2, data_encoding::Bf, data_encoding::Bf, data_encoding::Bf	44	7	15.90%
data_encoding::decode_wrap_mut::data_encoding::N2, data_encoding::Bt, data_encoding::Bf, data_encoding::Bf	44	7	15.90%
data_encoding::decode_wrap_mut::data_encoding::N3, data_encoding::Bf, data_encoding::Bf, data_encoding::Bf	44	7	15.90%
data_encoding::decode_wrap_mut::data_encoding::N3, data_encoding::Bt, data_encoding::Bf, data_encoding::Bf	44	7	15.90%
data_encoding::decode_wrap_mut::data_encoding::N4, data_encoding::Bf, data_encoding::Bf, data_encoding::Bf	44	7	15.90%
data_encoding::decode_wrap_mut::data_encoding::N4, data_encoding::Bt, data_encoding::Bf, data_encoding::Bf	44	7	15.90%
data_encoding::decode_wrap_mut::data_encoding::N5, data_encoding::Bf, data_encoding::Bf, data_encoding::Bf	44	7	15.90%
data_encoding::decode_wrap_mut::data_encoding::N5, data_encoding::Bt, data_encoding::Bf, data_encoding::Bf	44	7	15.90%
data_encoding::decode_wrap_mut::data_encoding::N6, data_encoding::Bf, data_encoding::Bf, data_encoding::Bf	44	7	15.90%
data_encoding::decode_wrap_mut::data_encoding::N6, data_encoding::Bt, data_encoding::Bf, data_encoding::Bf	44	7	15.90%
data_encoding::decode_wrap_mut::data_encoding::N3, data_encoding::Bf, data_encoding::Bt, data_encoding::Bf	44	7	15.90%
data_encoding::decode_wrap_mut::data_encoding::N3, data_encoding::Bt, data_encoding::Bt, data_encoding::Bf	44	7	15.90%
data_encoding::decode_wrap_mut::data_encoding::N5, data_encoding::Bf, data_encoding::Bt, data_encoding::Bf	44	7	15.90%
data_encoding::decode_wrap_mut::data_encoding::N5, data_encoding::Bt, data_encoding::Bt, data_encoding::Bf	44	7	15.90%
data_encoding::decode_wrap_mut::data_encoding::N6, data_encoding::Bf, data_encoding::Bt, data_encoding::Bf	44	7	15.90%
data_encoding::decode_wrap_mut::data_encoding::N6, data_encoding::Bt, data_encoding::Bt, data_encoding::Bf	44	7	15.90%

New fuzzers

The below fuzzers are templates and suggestions for how to target the set of optimal functions above

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/data-encoding/lib/fuzz/fuzz_targets/impl_encode.rs	['impl_encode']	[]
/src/data-encoding/lib/fuzz/fuzz_targets/impl_decode.rs	['impl_decode']	[]
/src/data-encoding/lib/fuzz/src/cmd.rs	['fuzz_any_spec', 'spec_spec_base', 'impl_new_encoder', 'impl_encode_write_buffer', 'impl_encode_mut_str', 'impl_encode_append', 'spec_decode_encode', 'impl_encode', 'impl_decode', 'spec_encode_decode', 'template']	['fuzz_any_spec', 'spec_spec_base', 'impl_new_encoder', 'impl_encode_write_buffer', 'impl_encode_mut_str', 'impl_encode_append', 'spec_decode_encode', 'impl_encode', 'impl_decode', 'spec_encode_decode', 'template']
/src/data-encoding/lib/macro/internal/src/lib.rs	['fuzz_any_spec', 'spec_spec_base', 'impl_new_encoder', 'impl_encode_write_buffer', 'impl_encode_mut_str', 'impl_encode_append', 'spec_decode_encode', 'impl_encode', 'impl_decode', 'spec_encode_decode', 'template']	[]
/src/data-encoding/www/src/lib.rs	['fuzz_any_spec', 'spec_spec_base', 'impl_new_encoder', 'impl_encode_write_buffer', 'impl_encode_mut_str', 'impl_encode_append', 'spec_decode_encode', 'impl_encode', 'impl_decode', 'spec_encode_decode', 'template']	[]
/src/data-encoding/lib/fuzz/fuzz_targets/fuzz_any_spec.rs	['fuzz_any_spec']	[]
/src/data-encoding/nostd/src/main.rs	['fuzz_any_spec', 'spec_spec_base', 'impl_new_encoder', 'impl_encode_write_buffer', 'impl_encode_mut_str', 'impl_encode_append', 'spec_decode_encode', 'impl_encode', 'impl_decode', 'spec_encode_decode', 'template']	[]
/src/data-encoding/lib/fuzz/fuzz_targets/spec_encode_decode.rs	['spec_encode_decode']	[]
/src/data-encoding/cmp/tests/lib.rs	[]	[]
/src/data-encoding/xtask/src/main.rs	[]	[]
/src/data-encoding/lib/macro/src/lib.rs	[]	[]
/src/data-encoding/lib/src/lib.rs	['fuzz_any_spec', 'spec_spec_base', 'impl_new_encoder', 'impl_encode_write_buffer', 'impl_encode_mut_str', 'impl_encode_append', 'spec_decode_encode', 'impl_encode', 'impl_decode', 'spec_encode_decode', 'template']	['fuzz_any_spec', 'spec_spec_base', 'impl_new_encoder', 'impl_encode_write_buffer', 'impl_encode_mut_str', 'impl_encode_append', 'spec_decode_encode', 'impl_encode', 'impl_decode', 'spec_encode_decode', 'template']
/src/data-encoding/www/src/state.rs	['fuzz_any_spec', 'spec_spec_base', 'impl_new_encoder', 'impl_encode_write_buffer', 'impl_encode_mut_str', 'impl_encode_append', 'spec_decode_encode', 'impl_encode', 'impl_decode', 'spec_encode_decode', 'template']	[]
/src/data-encoding/lib/fuzz/examples/analyze.rs	['fuzz_any_spec', 'spec_spec_base', 'impl_new_encoder', 'impl_encode_write_buffer', 'impl_encode_mut_str', 'impl_encode_append', 'spec_decode_encode', 'impl_encode', 'impl_decode', 'spec_encode_decode', 'template']	['fuzz_any_spec', 'spec_spec_base', 'impl_new_encoder', 'impl_encode_write_buffer', 'impl_encode_mut_str', 'impl_encode_append', 'spec_decode_encode', 'impl_encode', 'impl_decode', 'spec_encode_decode', 'template']
/src/data-encoding/www/src/utf8.rs	['fuzz_any_spec', 'spec_spec_base', 'impl_new_encoder', 'impl_encode_write_buffer', 'impl_encode_mut_str', 'impl_encode_append', 'spec_decode_encode', 'impl_encode', 'impl_decode', 'spec_encode_decode', 'template']	[]
/src/data-encoding/cmp/src/lib.rs	[]	[]
/src/data-encoding/lib/macro/tests/lib.rs	[]	[]
/src/data-encoding/lib/fuzz/fuzz_targets/spec_spec_base.rs	['spec_spec_base']	[]
/src/data-encoding/lib/tests/lib.rs	['fuzz_any_spec', 'spec_spec_base', 'impl_new_encoder', 'impl_encode_write_buffer', 'impl_encode_mut_str', 'impl_encode_append', 'spec_decode_encode', 'impl_encode', 'impl_decode', 'spec_encode_decode', 'template']	['impl_new_encoder', 'template']
/src/data-encoding/lib/fuzz/fuzz_targets/impl_encode_write_buffer.rs	['impl_encode_write_buffer']	[]
/src/data-encoding/lib/v3/src/lib.rs	['fuzz_any_spec', 'spec_spec_base', 'impl_new_encoder', 'impl_encode_write_buffer', 'impl_encode_mut_str', 'impl_encode_append', 'spec_decode_encode', 'impl_encode', 'impl_decode', 'spec_encode_decode', 'template']	['fuzz_any_spec', 'spec_spec_base', 'impl_new_encoder', 'impl_encode_write_buffer', 'impl_encode_mut_str', 'impl_encode_append', 'spec_decode_encode', 'impl_encode', 'impl_decode', 'spec_encode_decode', 'template']
/src/data-encoding/cmp/benches/lib.rs	[]	[]
/src/data-encoding/lib/fuzz/fuzz_targets/impl_encode_mut_str.rs	['impl_encode_mut_str']	[]
/src/data-encoding/bin/src/main.rs	['fuzz_any_spec', 'spec_spec_base', 'impl_new_encoder', 'impl_encode_write_buffer', 'impl_encode_mut_str', 'impl_encode_append', 'spec_decode_encode', 'impl_encode', 'impl_decode', 'spec_encode_decode', 'template']	['impl_new_encoder', 'impl_encode_write_buffer', 'impl_encode_mut_str', 'impl_encode_append', 'spec_decode_encode', 'impl_encode', 'spec_encode_decode', 'template']
/src/data-encoding/lib/fuzz/fuzz_targets/template.rs	['template']	[]
/src/data-encoding/lib/benches/lib.rs	[]	[]
/src/data-encoding/lib/fuzz/src/gen.rs	['fuzz_any_spec', 'spec_spec_base', 'impl_new_encoder', 'impl_encode_write_buffer', 'impl_encode_mut_str', 'impl_encode_append', 'spec_decode_encode', 'impl_encode', 'impl_decode', 'spec_encode_decode', 'template']	['fuzz_any_spec', 'spec_spec_base', 'impl_new_encoder', 'impl_encode_write_buffer', 'impl_encode_mut_str', 'impl_encode_append', 'spec_decode_encode', 'impl_encode', 'impl_decode', 'spec_encode_decode', 'template']
/src/data-encoding/lib/fuzz/fuzz_targets/impl_encode_append.rs	['impl_encode_append']	[]
/src/data-encoding/lib/fuzz/fuzz_targets/spec_decode_encode.rs	['spec_decode_encode']	[]
/src/data-encoding/lib/fuzz/src/spec.rs	['fuzz_any_spec', 'spec_spec_base', 'impl_new_encoder', 'impl_encode_write_buffer', 'impl_encode_mut_str', 'impl_encode_append', 'spec_decode_encode', 'impl_encode', 'impl_decode', 'spec_encode_decode', 'template']	['fuzz_any_spec', 'spec_spec_base', 'impl_new_encoder', 'impl_encode_write_buffer', 'impl_encode_mut_str', 'impl_encode_append', 'spec_decode_encode', 'impl_encode', 'impl_decode', 'spec_encode_decode', 'template']
/src/data-encoding/www/src/range.rs	[]	[]
/src/data-encoding/lib/v3/tests/lib.rs	[]	[]
/src/data-encoding/lib/fuzz/fuzz_targets/impl_new_encoder.rs	['impl_new_encoder']	[]

Directories in report

Directory
/src/data-encoding/lib/macro/internal/src/
/src/data-encoding/lib/v3/src/
/src/data-encoding/bin/src/
/src/data-encoding/lib/v3/tests/
/src/data-encoding/cmp/tests/
/src/data-encoding/lib/fuzz/fuzz_targets/
/src/data-encoding/lib/src/
/src/data-encoding/lib/fuzz/src/
/src/data-encoding/xtask/src/
/src/data-encoding/cmp/benches/
/src/data-encoding/cmp/src/
/src/data-encoding/www/src/
/src/data-encoding/nostd/src/
/src/data-encoding/lib/benches/
/src/data-encoding/lib/macro/tests/
/src/data-encoding/lib/fuzz/examples/
/src/data-encoding/lib/macro/src/
/src/data-encoding/lib/tests/

This section shows a list of 3rd party function calls and their relative coverage information. By static analysis of the target project code, all of the 3rd party function call and their caller information, including the source file and line number that initiate the call are captured. The caller source code file and line number are shown in column 2 while column 1 is the function name of the 3rd party function call. Each occurrent of the 3rd party function call will occuply a separate row. Column 3 of each row indicate if the 3rd party call in the source file line is unreachable. Column 4 lists all fuzzers that have covered that particular system call in that specific location (source file and line)during their dynamic fuzzing.

Function in each files in report

Target sink	Callsite location	Reached by fuzzer	Covered by Fuzzers