High level conclusions

Fuzzers reach 71.79% code coverage.

Fuzzers reach 27.48% of cyclomatic complexity.

Fuzzers reach 32.69% of all functions.

Reachability and coverage overview

Functions statically reachable by fuzzers

459 / 1404

Cyclomatic complexity statically reachable by fuzzers

2976 / 10827

Runtime code coverage of functions

1008 / 1404

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: jq_fuzz_load_file

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	387	50.6%
gold	[1:9]	9	1.17%
yellow	[10:29]	3	0.39%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	365	47.7%
All colors	764	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
222	339	scan	call site: 00339	jv_number_value
32	211	jv_array_set	call site: 00211	jv_array_slice
22	12	jv_string_vfmt	call site: 00012	memory_exhausted
10	593	jvp_object_unshare	call site: 00593	jvp_object_new
7	316	check_literal	call site: 00316	check_literal
6	297	decSetSubnormal	call site: 00297	decSetSubnormal
5	64	jv_load_file	call site: 00064	jv_string_fmt
5	185	jv_array_set	call site: 00185	jv_string
5	244	jv_parser_next	call site: 00244	check_literal
5	325	parse_check_done	call site: 00325	parser_reset
5	604	jvp_object_buckets	call site: 00604	jv_free
4	7	jv_load_file	call site: 00007	jv_string_fmt

Runtime coverage analysis

Covered functions

114

Functions that are reachable but not covered

91

Reachable functions

205

Percentage of reachable functions covered

55.61%

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
tests/jq_fuzz_load_file.c	1
src/jv_file.c	1
src/jv.c	78
src/jv_alloc.c	8
src/jv_unicode.c	5
src/jv_parse.c	24
src/jv_dtoa.c	24
src/jv.h	1
vendor/decNumber/decContext.c	3
vendor/decNumber/decNumber.c	24
src/jv_dtoa_tsd.c	4

Fuzzer: jq_fuzz_parse

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	370	51.3%
gold	[1:9]	9	1.24%
yellow	[10:29]	2	0.27%
greenyellow	[30:49]	9	1.24%
lawngreen	50+	331	45.9%
All colors	721	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
222	278	scan	call site: 00278	jv_number_value
32	150	jv_array_set	call site: 00150	jv_array_slice
22	10	jvp_array_alloc	call site: 00010	memory_exhausted
10	532	jvp_object_unshare	call site: 00532	jvp_object_new
7	255	check_literal	call site: 00255	check_literal
6	236	decSetSubnormal	call site: 00236	decSetSubnormal
5	124	jv_array_set	call site: 00124	jv_string
5	183	jv_parser_next	call site: 00183	check_literal
5	264	parse_check_done	call site: 00264	parser_reset
5	543	jvp_object_buckets	call site: 00543	jv_free
4	131	jvp_array_offset	call site: 00131	jv_string
4	606	jvp_object_write	call site: 00606	jv_string

Runtime coverage analysis

Covered functions

111

Functions that are reachable but not covered

76

Reachable functions

187

Percentage of reachable functions covered

59.36%

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
tests/jq_fuzz_parse.c	1
src/jv_parse.c	25
src/jv.c	75
src/jv_alloc.c	8
src/jv_dtoa.c	24
src/jv_unicode.c	4
src/jv.h	1
vendor/decNumber/decContext.c	3
vendor/decNumber/decNumber.c	24
src/jv_dtoa_tsd.c	4

Fuzzer: jq_fuzz_parse_stream

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	360	52.0%
gold	[1:9]	14	2.02%
yellow	[10:29]	2	0.28%
greenyellow	[30:49]	1	0.14%
lawngreen	50+	315	45.5%
All colors	692	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
134	304	jv_number_value	call site: 00304	jvp_literal_number_to_double
131	502	scan	call site: 00502	jv_object_set
22	2	jv_parser_new	call site: 00002	memory_exhausted
14	253	check_literal	call site: 00253	check_literal
6	234	decSetSubnormal	call site: 00234	decSetSubnormal
5	122	jv_array_set	call site: 00122	jv_string
5	181	jv_parser_next	call site: 00181	check_literal
4	129	jvp_array_offset	call site: 00129	jv_string
4	651	jv_string_vfmt	call site: 00651	jv_array_append
3	162	jvp_array_slice	call site: 00162	jv_array_get
2	51	jv_string_sized	call site: 00051	jv_string
2	176	jv_array_get	call site: 00176	jv_array_append

Runtime coverage analysis

Covered functions

93

Functions that are reachable but not covered

89

Reachable functions

182

Percentage of reachable functions covered

51.1%

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
tests/jq_fuzz_parse_stream.c	1
src/jv_parse.c	24
src/jv_alloc.c	8
src/jv.c	71
src/jv_dtoa.c	24
src/jv_unicode.c	4
src/jv.h	1
vendor/decNumber/decContext.c	3
vendor/decNumber/decNumber.c	24
src/jv_dtoa_tsd.c	4
./src/jv.h	1

Fuzzer: jq_fuzz_parse_extended

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	245	24.8%
gold	[1:9]	47	4.77%
yellow	[10:29]	32	3.25%
greenyellow	[30:49]	3	0.30%
lawngreen	50+	657	66.7%
All colors	984	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
38	820	jvp_dtoa	call site: 00820	pow5mult
30	394	diff	call site: 00394	bigcomp
22	9	jvp_array_alloc	call site: 00009	memory_exhausted
22	728	put_str	call site: 00728	jv_string_append_buf
10	429	quorem	call site: 00429	multadd
10	531	jvp_object_unshare	call site: 00531	jvp_object_new
8	354	jvp_strtod	call site: 00354	s2b
6	235	decSetSubnormal	call site: 00235	decSetSubnormal
6	363	Balloc	call site: 00363	d2b
5	123	jv_array_set	call site: 00123	jv_string
5	542	jvp_object_buckets	call site: 00542	jv_free
5	937	jv_keys	call site: 00937	jv_array_set

Runtime coverage analysis

Covered functions

180

Functions that are reachable but not covered

44

Reachable functions

222

Percentage of reachable functions covered

80.18%

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
tests/jq_fuzz_parse_extended.c	1
src/jv_parse.c	24
src/jv.c	91
src/jv_alloc.c	9
src/jv_dtoa.c	29
src/jv_unicode.c	4
src/jv.h	1
vendor/decNumber/decContext.c	3
vendor/decNumber/decNumber.c	24
src/jv_dtoa_tsd.c	4
./src/jv.h	1
src/jv_print.c	9
src/jv_aux.c	2

Fuzzer: jq_fuzz_compile

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	1469	47.4%
gold	[1:9]	102	3.29%
yellow	[10:29]	32	1.03%
greenyellow	[30:49]	144	4.64%
lawngreen	50+	1351	43.6%
All colors	3098	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
101	2009	gen_param	call site: 02009	gen_binop
92	294	yy_push_state	call site: 00294	jv_parse_sized
91	671	quorem	call site: 00671	parse_token
78	2170	gen_foreach	call site: 02170	gen_array_matcher
77	2628	process_dependencies	call site: 02628	load_library
50	2706	block_has_only_binders_and_imports	call site: 02706	process_dependencies
47	2251	gen_object_matcher	call site: 02251	check_object_key
40	2301	gen_dictpair	call site: 02301	check_object_key
38	1533	jvp_dtoa	call site: 01533	pow5mult
38	1915	gen_error	call site: 01915	gen_update
28	518	tokenadd	call site: 00518	stream_token
26	128	jv_free	call site: 00128	jv_array_slice

Runtime coverage analysis

Covered functions

382

Functions that are reachable but not covered

109

Reachable functions

487

Percentage of reachable functions covered

77.62%

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
tests/jq_fuzz_compile.c	1
src/execute.c	23
src/jv_alloc.c	11
src/exec_stack.h	7
src/jv.c	112
src/locfile.c	6
src/jv_unicode.c	5
src/jv.h	1
src/bytecode.c	8
src/linker.c	9
src/parser.y	14
src/lexer.c	23
src/lexer.l	5
src/compile.c	81
src/parser.c	6
src/jv_parse.c	26
src/jv_dtoa.c	29
vendor/decNumber/decContext.c	3
vendor/decNumber/decNumber.c	26
src/jv_dtoa_tsd.c	4
src/builtin.c	17
src/jv_print.c	11
src/jv_aux.c	5
src/util.c	4
src/jv_file.c	1

Fuzzer: jq_fuzz_fixed

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	1445	40.6%
gold	[1:9]	98	2.75%
yellow	[10:29]	39	1.09%
greenyellow	[30:49]	8	0.22%
lawngreen	50+	1961	55.2%
All colors	3551	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
101	2012	gen_param	call site: 02012	gen_binop
93	381	yy_push_state	call site: 00381	jv_parse_sized
83	2624	process_dependencies	call site: 02624	load_library
69	759	quorem	call site: 00759	jv_array_slice
58	2303	gen_dictpair	call site: 02303	check_object_key
55	3081	jq_next	call site: 03081	dump_operation
50	2708	block_has_only_binders_and_imports	call site: 02708	process_dependencies
47	2253	gen_object_matcher	call site: 02253	check_object_key
46	1910	binop_greatereq	call site: 01910	gen_update
46	2173	gen_foreach	call site: 02173	gen_lambda
38	1536	jvp_dtoa	call site: 01536	pow5mult
27	607	scan	call site: 00607	jv_number_value

Runtime coverage analysis

Covered functions

701

Functions that are reachable but not covered

98

Reachable functions

506

Percentage of reachable functions covered

80.63%

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
./tests/jq_fuzz_fixed.cpp	1
src/execute.c	34
src/jv_alloc.c	11
src/exec_stack.h	9
src/jv.c	115
src/jv_unicode.c	5
src/locfile.c	6
src/jv.h	1
src/bytecode.c	6
src/linker.c	9
src/parser.y	14
src/lexer.c	23
src/lexer.l	5
src/compile.c	81
src/parser.c	6
src/jv_parse.c	27
src/jv_dtoa.c	29
vendor/decNumber/decContext.c	3
vendor/decNumber/decNumber.c	26
src/jv_dtoa_tsd.c	4
src/builtin.c	17
src/jv_print.c	11
src/jv_aux.c	7
src/util.c	4
src/jv_file.c	1
./src/jv.h	1

Fuzzer: jq_fuzz_execute

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	1310	36.8%
gold	[1:9]	55	1.54%
yellow	[10:29]	8	0.22%
greenyellow	[30:49]	28	0.78%
lawngreen	50+	2153	60.5%
All colors	3554	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
101	2012	gen_param	call site: 02012	gen_binop
92	382	yy_push_state	call site: 00382	jv_parse_sized
77	2631	process_dependencies	call site: 02631	load_library
69	759	quorem	call site: 00759	jv_array_slice
53	3084	jq_next	call site: 03084	dump_operation
50	2709	block_has_only_binders_and_imports	call site: 02709	process_dependencies
47	2173	gen_foreach	call site: 02173	gen_lambda
47	2254	gen_object_matcher	call site: 02254	check_object_key
40	2304	gen_dictpair	call site: 02304	check_object_key
38	1536	jvp_dtoa	call site: 01536	pow5mult
38	1918	gen_error	call site: 01918	gen_update
27	607	scan	call site: 00607	jv_number_value

Runtime coverage analysis

Covered functions

987

Functions that are reachable but not covered

88

Reachable functions

506

Percentage of reachable functions covered

82.61%

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
./tests/jq_fuzz_execute.cpp	1
src/execute.c	34
src/jv_alloc.c	11
src/exec_stack.h	9
src/jv.c	115
src/jv_unicode.c	5
src/locfile.c	6
src/jv.h	1
src/bytecode.c	6
src/linker.c	9
src/parser.y	14
src/lexer.c	23
src/lexer.l	5
src/compile.c	81
src/parser.c	6
src/jv_parse.c	27
src/jv_dtoa.c	29
vendor/decNumber/decContext.c	3
vendor/decNumber/decNumber.c	26
src/jv_dtoa_tsd.c	4
src/builtin.c	17
src/jv_print.c	11
src/jv_aux.c	7
src/util.c	4
src/jv_file.c	1
./src/jv.h	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
f_match	/src/jq/src/builtin.c	7	['N/A', 'size_t', 'N/A', 'size_t', 'N/A', 'N/A', 'N/A']	18	0	2145	97	28	624	0	6201	4819
decNumberPower	/src/jq/vendor/decNumber/decNumber.c	4	['N/A', 'N/A', 'N/A', 'N/A']	8	0	1034	161	60	34	0	776	418
onig_regset_search	/src/jq/vendor/oniguruma/src/regexec.c	8	['N/A', 'N/A', 'N/A', 'N/A', 'N/A', 'int', 'int', 'N/A']	11	0	127	14	5	45	0	1054	106
f_delpaths	/src/jq/src/builtin.c	5	['N/A', 'size_t', 'N/A', 'size_t', 'N/A']	19	0	40	3	2	219	0	1575	104
onig_setup_builtin_monitors_by_ascii_encoded_name	/src/jq/vendor/oniguruma/src/regexec.c	1	['N/A']	6	0	73	11	4	34	0	184	100
get_case_fold_codes_by_str	/src/jq/vendor/oniguruma/src/utf8.c	4	['int', 'N/A', 'N/A', 'N/A']	4	0	24	3	2	8	0	91	79
detect_can_be_slow	/src/jq/vendor/oniguruma/src/regcomp.c	4	['N/A', 'N/A', 'int', 'N/A']	3	0	612	102	28	2	2	74	74
f_format	/src/jq/src/builtin.c	5	['N/A', 'size_t', 'N/A', 'size_t', 'N/A']	18	0	1945	178	53	185	0	1322	64
jq_util_input_next_input_cb	/src/jq/src/util.c	2	['N/A', 'N/A']	17	0	25	3	2	198	0	1382	52
decNumberSquareRoot	/src/jq/vendor/decNumber/decNumber.c	3	['N/A', 'N/A', 'N/A']	6	0	1014	116	42	26	0	571	42

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

Functions statically reachable by fuzzers

942 / 1404

Cyclomatic complexity statically reachable by fuzzers

8798 / 10827

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.

tests/jq_fuzz_load_file.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=['scan', 'jv_array_set', 'jv_string_vfmt', 'jvp_object_unshare', 'check_literal', 'decSetSubnormal', 'jv_load_file', 'jv_parser_next', 'parse_check_done']

tests/jq_fuzz_parse.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=['scan', 'jv_array_set', 'jvp_array_alloc', 'jvp_object_unshare', 'check_literal', 'decSetSubnormal', 'jv_parser_next', 'parse_check_done', 'jvp_object_buckets']

tests/jq_fuzz_parse_stream.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=['jv_number_value', 'scan', 'jv_parser_new', 'check_literal', 'decSetSubnormal', 'jv_array_set', 'jv_parser_next', 'jvp_array_offset', 'jv_string_vfmt', 'jvp_array_slice']

tests/jq_fuzz_parse_extended.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=['jvp_dtoa', 'diff', 'jvp_array_alloc', 'put_str', 'quorem', 'jvp_object_unshare', 'jvp_strtod', 'decSetSubnormal', 'Balloc', 'jv_array_set']

tests/jq_fuzz_compile.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=['gen_param', 'yy_push_state', 'quorem', 'gen_foreach', 'process_dependencies', 'block_has_only_binders_and_imports', 'gen_object_matcher', 'gen_dictpair', 'jvp_dtoa', 'gen_error']

./tests/jq_fuzz_fixed.cpp

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_param', 'yy_push_state', 'process_dependencies', 'quorem', 'gen_dictpair', 'jq_next', 'block_has_only_binders_and_imports', 'gen_object_matcher', 'binop_greatereq', 'gen_foreach']

./tests/jq_fuzz_execute.cpp

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_param', 'yy_push_state', 'process_dependencies', 'quorem', 'jq_next', 'block_has_only_binders_and_imports', 'gen_foreach', 'gen_object_matcher', 'gen_dictpair', 'jvp_dtoa']

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
decContextDefault	39	21	53.84%	['jq_fuzz_compile', 'jq_fuzz_parse', 'jq_fuzz_fixed', 'jq_fuzz_load_file', 'jq_fuzz_execute', 'jq_fuzz_parse_extended', 'jq_fuzz_parse_stream']
decApplyRound	94	36	38.29%	['jq_fuzz_compile', 'jq_fuzz_parse', 'jq_fuzz_fixed', 'jq_fuzz_load_file', 'jq_fuzz_execute', 'jq_fuzz_parse_extended', 'jq_fuzz_parse_stream']
jvp_dtoa	273	120	43.95%	['jq_fuzz_execute', 'jq_fuzz_parse_extended', 'jq_fuzz_compile', 'jq_fuzz_fixed']
yy_get_next_buffer	90	19	21.11%	['jq_fuzz_execute', 'jq_fuzz_fixed', 'jq_fuzz_compile']
process_dependencies	79	42	53.16%	['jq_fuzz_execute', 'jq_fuzz_fixed', 'jq_fuzz_compile']
decCompareOp	91	23	25.27%	['jq_fuzz_execute', 'jq_fuzz_fixed', 'jq_fuzz_compile']
decAddOp	174	47	27.01%	['jq_fuzz_execute', 'jq_fuzz_fixed']
compile_anchor_look_behind_node	103	23	22.33%	['jq_fuzz_execute']
compile_anchor_look_behind_not_node	116	30	25.86%	['jq_fuzz_execute']
onig_error_code_to_format	166	82	49.39%	['jq_fuzz_execute']
to_ascii	45	16	35.55%	['jq_fuzz_execute']
prs_callout_of_name	136	67	49.26%	['jq_fuzz_execute']
prs_callout_args	138	72	52.17%	['jq_fuzz_execute']
add_ctype_to_cc	91	15	16.48%	['jq_fuzz_execute']

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/jq/src/builtin.c	['jq_fuzz_compile', 'jq_fuzz_fixed', 'jq_fuzz_execute']	['jq_fuzz_compile', 'jq_fuzz_fixed', 'jq_fuzz_execute']
/src/jq/./tests/jq_fuzz_fixed.cpp	['jq_fuzz_fixed']	[]
/src/jq/src/jv.h	['jq_fuzz_load_file', 'jq_fuzz_parse', 'jq_fuzz_parse_stream', 'jq_fuzz_parse_extended', 'jq_fuzz_compile', 'jq_fuzz_fixed', 'jq_fuzz_execute']	['jq_fuzz_load_file', 'jq_fuzz_parse', 'jq_fuzz_parse_stream', 'jq_fuzz_parse_extended', 'jq_fuzz_compile', 'jq_fuzz_fixed', 'jq_fuzz_execute']
/src/jq/src/jv_dtoa.c	['jq_fuzz_load_file', 'jq_fuzz_parse', 'jq_fuzz_parse_stream', 'jq_fuzz_parse_extended', 'jq_fuzz_compile', 'jq_fuzz_fixed', 'jq_fuzz_execute']	['jq_fuzz_load_file', 'jq_fuzz_parse', 'jq_fuzz_parse_stream', 'jq_fuzz_parse_extended', 'jq_fuzz_compile', 'jq_fuzz_fixed', 'jq_fuzz_execute']
/src/jq/tests/jq_fuzz_load_file.c	['jq_fuzz_load_file']	['jq_fuzz_load_file']
/src/jq/src/jv_aux.c	['jq_fuzz_parse_extended', 'jq_fuzz_compile', 'jq_fuzz_fixed', 'jq_fuzz_execute']	['jq_fuzz_parse_extended', 'jq_fuzz_compile', 'jq_fuzz_fixed', 'jq_fuzz_execute']
/src/jq/src/bytecode.c	['jq_fuzz_compile', 'jq_fuzz_fixed', 'jq_fuzz_execute']	['jq_fuzz_compile', 'jq_fuzz_fixed', 'jq_fuzz_execute']
/src/jq/vendor/decNumber/decNumber.c	['jq_fuzz_load_file', 'jq_fuzz_parse', 'jq_fuzz_parse_stream', 'jq_fuzz_parse_extended', 'jq_fuzz_compile', 'jq_fuzz_fixed', 'jq_fuzz_execute']	['jq_fuzz_load_file', 'jq_fuzz_parse', 'jq_fuzz_parse_stream', 'jq_fuzz_parse_extended', 'jq_fuzz_compile', 'jq_fuzz_fixed', 'jq_fuzz_execute']
/src/jq/vendor/oniguruma/src/ascii.c	[]	[]
/src/jq/src/jv_print.c	['jq_fuzz_parse_extended', 'jq_fuzz_compile', 'jq_fuzz_fixed', 'jq_fuzz_execute']	['jq_fuzz_parse_extended', 'jq_fuzz_compile', 'jq_fuzz_fixed', 'jq_fuzz_execute']
/src/jq/tests/jq_fuzz_parse_extended.c	['jq_fuzz_parse_extended']	['jq_fuzz_parse_extended']
/src/jq/src/linker.c	['jq_fuzz_compile', 'jq_fuzz_fixed', 'jq_fuzz_execute']	['jq_fuzz_compile', 'jq_fuzz_fixed', 'jq_fuzz_execute']
/src/jq/vendor/oniguruma/src/unicode_fold1_key.c	[]	[]
/src/jq/vendor/oniguruma/src/regsyntax.c	[]	[]
/src/jq/tests/jq_fuzz_parse.c	['jq_fuzz_parse']	['jq_fuzz_parse']
/src/jq/vendor/oniguruma/src/regerror.c	[]	[]
/src/jq/tests/jq_fuzz_parse_stream.c	['jq_fuzz_parse_stream']	['jq_fuzz_parse_stream']
/src/jq/src/locfile.c	['jq_fuzz_compile', 'jq_fuzz_fixed', 'jq_fuzz_execute']	['jq_fuzz_compile', 'jq_fuzz_fixed', 'jq_fuzz_execute']
/src/jq/src/lexer.l	['jq_fuzz_compile', 'jq_fuzz_fixed', 'jq_fuzz_execute']	['jq_fuzz_compile', 'jq_fuzz_fixed', 'jq_fuzz_execute']
/src/jq/./src/jv.h	['jq_fuzz_parse_stream', 'jq_fuzz_parse_extended', 'jq_fuzz_fixed', 'jq_fuzz_execute']	['jq_fuzz_load_file', 'jq_fuzz_parse', 'jq_fuzz_parse_stream', 'jq_fuzz_parse_extended', 'jq_fuzz_compile', 'jq_fuzz_fixed', 'jq_fuzz_execute']
/src/jq/tests/jq_fuzz_compile.c	['jq_fuzz_compile']	['jq_fuzz_compile']
/src/jq/vendor/oniguruma/src/unicode_unfold_key.c	[]	[]
/src/jq/vendor/decNumber/decContext.c	['jq_fuzz_load_file', 'jq_fuzz_parse', 'jq_fuzz_parse_stream', 'jq_fuzz_parse_extended', 'jq_fuzz_compile', 'jq_fuzz_fixed', 'jq_fuzz_execute']	['jq_fuzz_load_file', 'jq_fuzz_parse', 'jq_fuzz_parse_stream', 'jq_fuzz_parse_extended', 'jq_fuzz_compile', 'jq_fuzz_fixed', 'jq_fuzz_execute']
/src/jq/vendor/oniguruma/src/utf8.c	[]	[]
/src/jq/src/lexer.c	['jq_fuzz_compile', 'jq_fuzz_fixed', 'jq_fuzz_execute']	['jq_fuzz_compile', 'jq_fuzz_fixed', 'jq_fuzz_execute']
/src/jq/src/jv_alloc.c	['jq_fuzz_load_file', 'jq_fuzz_parse', 'jq_fuzz_parse_stream', 'jq_fuzz_parse_extended', 'jq_fuzz_compile', 'jq_fuzz_fixed', 'jq_fuzz_execute']	['jq_fuzz_load_file', 'jq_fuzz_parse', 'jq_fuzz_parse_stream', 'jq_fuzz_parse_extended', 'jq_fuzz_compile', 'jq_fuzz_fixed', 'jq_fuzz_execute']
/src/jq/vendor/oniguruma/src/regenc.c	[]	[]
/src/jq/src/jv_dtoa_tsd.c	['jq_fuzz_load_file', 'jq_fuzz_parse', 'jq_fuzz_parse_stream', 'jq_fuzz_parse_extended', 'jq_fuzz_compile', 'jq_fuzz_fixed', 'jq_fuzz_execute']	['jq_fuzz_parse_extended', 'jq_fuzz_compile', 'jq_fuzz_fixed', 'jq_fuzz_execute']
/src/jq/./tests/jq_fuzz_execute.cpp	['jq_fuzz_execute']	[]
/src/jq/vendor/oniguruma/src/regcomp.c	[]	[]
/src/jq/src/exec_stack.h	['jq_fuzz_compile', 'jq_fuzz_fixed', 'jq_fuzz_execute']	['jq_fuzz_compile', 'jq_fuzz_fixed', 'jq_fuzz_execute']
/src/jq/src/execute.c	['jq_fuzz_compile', 'jq_fuzz_fixed', 'jq_fuzz_execute']	['jq_fuzz_compile', 'jq_fuzz_fixed', 'jq_fuzz_execute']
/src/jq/src/parser.c	['jq_fuzz_compile', 'jq_fuzz_fixed', 'jq_fuzz_execute']	['jq_fuzz_compile', 'jq_fuzz_fixed', 'jq_fuzz_execute']
/src/jq/src/jv.c	['jq_fuzz_load_file', 'jq_fuzz_parse', 'jq_fuzz_parse_stream', 'jq_fuzz_parse_extended', 'jq_fuzz_compile', 'jq_fuzz_fixed', 'jq_fuzz_execute']	['jq_fuzz_load_file', 'jq_fuzz_parse', 'jq_fuzz_parse_stream', 'jq_fuzz_parse_extended', 'jq_fuzz_compile', 'jq_fuzz_fixed', 'jq_fuzz_execute']
/src/jq/src/util.c	['jq_fuzz_compile', 'jq_fuzz_fixed', 'jq_fuzz_execute']	['jq_fuzz_compile', 'jq_fuzz_fixed', 'jq_fuzz_execute']
/src/jq/vendor/oniguruma/src/unicode_fold2_key.c	[]	[]
/src/jq/vendor/oniguruma/src/unicode.c	[]	[]
/src/jq/src/compile.c	['jq_fuzz_compile', 'jq_fuzz_fixed', 'jq_fuzz_execute']	['jq_fuzz_compile', 'jq_fuzz_fixed', 'jq_fuzz_execute']
/src/jq/src/jv_parse.c	['jq_fuzz_load_file', 'jq_fuzz_parse', 'jq_fuzz_parse_stream', 'jq_fuzz_parse_extended', 'jq_fuzz_compile', 'jq_fuzz_fixed', 'jq_fuzz_execute']	['jq_fuzz_load_file', 'jq_fuzz_parse', 'jq_fuzz_parse_stream', 'jq_fuzz_parse_extended', 'jq_fuzz_compile', 'jq_fuzz_fixed', 'jq_fuzz_execute']
/src/jq/vendor/oniguruma/src/st.c	[]	[]
/src/jq/src/libm.h	[]	[]
/src/jq/src/parser.y	['jq_fuzz_compile', 'jq_fuzz_fixed', 'jq_fuzz_execute']	['jq_fuzz_compile', 'jq_fuzz_fixed', 'jq_fuzz_execute']
/src/jq/vendor/oniguruma/src/./unicode_property_data.c	[]	[]
/src/jq/vendor/oniguruma/src/unicode_fold3_key.c	[]	[]
/src/jq/src/jv_file.c	['jq_fuzz_load_file', 'jq_fuzz_compile', 'jq_fuzz_fixed', 'jq_fuzz_execute']	['jq_fuzz_load_file']
/src/jq/vendor/oniguruma/src/regexec.c	[]	[]
/src/jq/vendor/oniguruma/src/regparse.c	[]	[]
/src/jq/src/jv_unicode.c	['jq_fuzz_load_file', 'jq_fuzz_parse', 'jq_fuzz_parse_stream', 'jq_fuzz_parse_extended', 'jq_fuzz_compile', 'jq_fuzz_fixed', 'jq_fuzz_execute']	['jq_fuzz_load_file', 'jq_fuzz_parse', 'jq_fuzz_parse_stream', 'jq_fuzz_parse_extended', 'jq_fuzz_compile', 'jq_fuzz_fixed', 'jq_fuzz_execute']

Directories in report

Directory
/src/jq/tests/
/src/jq/src/
/src/jq/./src/
/src/jq/./tests/
/src/jq/vendor/oniguruma/src/./
/src/jq/vendor/decNumber/
/src/jq/vendor/oniguruma/src/