High level conclusions

Fuzzers reach 71.64% code coverage.

Fuzzers reach 27.40% of cyclomatic complexity.

Fuzzers reach 32.64% of all functions.

Reachability and coverage overview

Functions statically reachable by fuzzers

457 / 1400

Cyclomatic complexity statically reachable by fuzzers

2954 / 10781

Runtime code coverage of functions

1003 / 1400

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_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	364	50.6%
gold	[1:9]	8	1.11%
yellow	[10:29]	2	0.27%
greenyellow	[30:49]	9	1.25%
lawngreen	50+	335	46.6%
All colors	718	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	281	scan	call site: 00281	jv_number_value
32	151	jv_array_set	call site: 00151	jv_array_slice
22	10	jvp_array_alloc	call site: 00010	memory_exhausted
10	535	jvp_object_unshare	call site: 00535	jvp_object_new
7	256	check_literal	call site: 00256	check_literal
6	237	decSetSubnormal	call site: 00237	decSetSubnormal
5	124	jv_array_set	call site: 00124	jv_string
5	184	jv_parser_next	call site: 00184	check_literal
5	265	parse_check_done	call site: 00265	parser_reset
5	546	jvp_object_buckets	call site: 00546	jvp_object_free
4	131	jvp_array_offset	call site: 00131	jv_string
3	602	jvp_object_write	call site: 00602	jv_string

Runtime coverage analysis

Covered functions

112

Functions that are reachable but not covered

73

Reachable functions

185

Percentage of reachable functions covered

60.54%

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	76
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_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	378	50.1%
gold	[1:9]	8	1.06%
yellow	[10:29]	3	0.39%
greenyellow	[30:49]	1	0.13%
lawngreen	50+	364	48.2%
All colors	754	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	338	scan	call site: 00338	jv_number_value
32	208	jv_array_set	call site: 00208	jv_array_slice
22	12	jv_string_vfmt	call site: 00012	memory_exhausted
10	592	jvp_object_unshare	call site: 00592	jvp_object_new
7	313	check_literal	call site: 00313	check_literal
6	294	decSetSubnormal	call site: 00294	decSetSubnormal
5	60	jv_load_file	call site: 00060	jv_string_fmt
5	182	jv_array_set	call site: 00182	jv_string
5	241	jv_parser_next	call site: 00241	check_literal
5	322	parse_check_done	call site: 00322	parser_reset
5	603	jvp_object_buckets	call site: 00603	jvp_object_free
4	7	jv_load_file	call site: 00007	jv_string_fmt

Runtime coverage analysis

Covered functions

115

Functions that are reachable but not covered

89

Reachable functions

204

Percentage of reachable functions covered

56.37%

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	79
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_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	351	48.9%
gold	[1:9]	31	4.32%
yellow	[10:29]	18	2.51%
greenyellow	[30:49]	7	0.97%
lawngreen	50+	310	43.2%
All colors	717	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	308	jv_number_value	call site: 00308	jvp_literal_number_to_double
123	506	scan	call site: 00506	jv_object_set
23	9	jvp_array_alloc	call site: 00009	memory_exhausted
14	255	check_literal	call site: 00255	check_literal
6	236	decSetSubnormal	call site: 00236	decSetSubnormal
5	123	jv_array_set	call site: 00123	jv_string
5	183	jv_parser_next	call site: 00183	check_literal
4	130	jvp_array_offset	call site: 00130	jv_string
3	164	jvp_array_slice	call site: 00164	jv_array_get
3	648	jv_string_vfmt	call site: 00648	jv_array_append
2	84	jvp_object_free	call site: 00084	jv_free
2	178	jv_array_get	call site: 00178	jv_array_append

Runtime coverage analysis

Covered functions

100

Functions that are reachable but not covered

84

Reachable functions

184

Percentage of reachable functions covered

54.35%

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.c	76
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_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	237	24.1%
gold	[1:9]	50	5.09%
yellow	[10:29]	28	2.85%
greenyellow	[30:49]	7	0.71%
lawngreen	50+	660	67.2%
All colors	982	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	814	jvp_dtoa	call site: 00814	pow5mult
30	397	diff	call site: 00397	bigcomp
22	9	jvp_array_alloc	call site: 00009	memory_exhausted
19	725	put_str	call site: 00725	jv_string_append_buf
10	432	quorem	call site: 00432	multadd
10	534	jvp_object_unshare	call site: 00534	jvp_object_new
8	357	jvp_strtod	call site: 00357	s2b
6	236	decSetSubnormal	call site: 00236	decSetSubnormal
6	366	Balloc	call site: 00366	d2b
5	123	jv_array_set	call site: 00123	jv_string
5	545	jvp_object_buckets	call site: 00545	jvp_object_free
5	747	jv_dump_term	call site: 00747	jvp_dump_string

Runtime coverage analysis

Covered functions

181

Functions that are reachable but not covered

41

Reachable functions

220

Percentage of reachable functions covered

81.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_extended.c	1
src/jv_parse.c	24
src/jv.c	92
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	1302	42.9%
gold	[1:9]	51	1.68%
yellow	[10:29]	22	0.72%
greenyellow	[30:49]	6	0.19%
lawngreen	50+	1652	54.4%
All colors	3033	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
100	1965	gen_param	call site: 01965	gen_binop
93	673	quorem	call site: 00673	parse_token
91	298	yy_push_state	call site: 00298	jv_parse_sized
71	2577	process_dependencies	call site: 02577	load_library
48	2123	gen_foreach	call site: 02123	gen_lambda
47	2204	gen_object_matcher	call site: 02204	check_object_key
44	2649	block_has_only_binders_and_imports	call site: 02649	process_dependencies
39	2254	gen_dictpair	call site: 02254	check_object_key
38	1509	jvp_dtoa	call site: 01509	pow5mult
38	1871	gen_error	call site: 01871	gen_update
29	1931	gen_import	call site: 01931	gen_function
28	520	tokenadd	call site: 00520	stream_token

Runtime coverage analysis

Covered functions

387

Functions that are reachable but not covered

99

Reachable functions

482

Percentage of reachable functions covered

79.46%

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	110
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	4
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	1397	39.9%
gold	[1:9]	83	2.37%
yellow	[10:29]	39	1.11%
greenyellow	[30:49]	33	0.94%
lawngreen	50+	1944	55.6%
All colors	3496	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
100	1968	gen_param	call site: 01968	gen_binop
92	377	yy_push_state	call site: 00377	jv_parse_sized
79	2571	process_dependencies	call site: 02571	load_library
70	753	quorem	call site: 00753	jv_array_slice
57	2256	gen_dictpair	call site: 02256	check_object_key
54	3011	jq_next	call site: 03011	dump_operation
47	2126	gen_foreach	call site: 02126	gen_lambda
47	2206	gen_object_matcher	call site: 02206	check_object_key
45	1867	binop_greatereq	call site: 01867	gen_update
44	2651	block_has_only_binders_and_imports	call site: 02651	process_dependencies
38	1512	jvp_dtoa	call site: 01512	pow5mult
29	1934	gen_import	call site: 01934	gen_function

Runtime coverage analysis

Covered functions

700

Functions that are reachable but not covered

94

Reachable functions

502

Percentage of reachable functions covered

81.27%

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

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

Function name	source code lines	source lines hit	percentage hit

Files reached

filename	functions hit
./tests/jq_fuzz_fixed.cpp	1
src/execute.c	34
src/jv_alloc.c	11
src/exec_stack.h	9
src/jv.c	114
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	6
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	1251	35.7%
gold	[1:9]	43	1.22%
yellow	[10:29]	17	0.48%
greenyellow	[30:49]	23	0.65%
lawngreen	50+	2164	61.8%
All colors	3498	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
100	1968	gen_param	call site: 01968	gen_binop
91	378	yy_push_state	call site: 00378	jv_parse_sized
71	2580	process_dependencies	call site: 02580	load_library
70	753	quorem	call site: 00753	jv_array_slice
52	3014	jq_next	call site: 03014	dump_operation
48	2126	gen_foreach	call site: 02126	gen_lambda
47	2207	gen_object_matcher	call site: 02207	check_object_key
44	2652	block_has_only_binders_and_imports	call site: 02652	process_dependencies
39	2257	gen_dictpair	call site: 02257	check_object_key
38	1512	jvp_dtoa	call site: 01512	pow5mult
38	1874	gen_error	call site: 01874	gen_update
29	1934	gen_import	call site: 01934	gen_function

Runtime coverage analysis

Covered functions

978

Functions that are reachable but not covered

85

Reachable functions

502

Percentage of reachable functions covered

83.07%

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	114
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	6
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']	16	0	2118	94	27	617	0	6170	4818
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
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
f_delpaths	/src/jq/src/builtin.c	5	['N/A', 'size_t', 'N/A', 'size_t', 'N/A']	17	0	40	3	2	187	0	1287	96
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']	16	0	1989	188	57	178	0	1297	68
jq_util_input_next_input_cb	/src/jq/src/util.c	2	['N/A', 'N/A']	17	0	25	3	2	194	0	1365	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

939 / 1400

Cyclomatic complexity statically reachable by fuzzers

8771 / 10781

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_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_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_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', 'jvp_array_alloc', 'check_literal', 'decSetSubnormal', 'jv_array_set', 'jv_parser_next', 'jvp_array_offset', 'jvp_array_slice', 'jv_string_vfmt']

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

./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', 'gen_foreach', 'gen_object_matcher', 'block_has_only_binders_and_imports', '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_parse_stream', 'jq_fuzz_parse_extended', 'jq_fuzz_compile', 'jq_fuzz_fixed', 'jq_fuzz_load_file', 'jq_fuzz_execute', 'jq_fuzz_parse']
decApplyRound	94	36	38.29%	['jq_fuzz_parse_stream', 'jq_fuzz_parse_extended', 'jq_fuzz_compile', 'jq_fuzz_fixed', 'jq_fuzz_load_file', 'jq_fuzz_execute', 'jq_fuzz_parse']
jvp_dtoa	273	120	43.95%	['jq_fuzz_fixed', 'jq_fuzz_parse_extended', 'jq_fuzz_execute', 'jq_fuzz_compile']
yy_get_next_buffer	90	19	21.11%	['jq_fuzz_fixed', 'jq_fuzz_execute', 'jq_fuzz_compile']
decCompareOp	91	23	25.27%	['jq_fuzz_fixed', 'jq_fuzz_execute', 'jq_fuzz_compile']
jv_set	79	43	54.43%	['jq_fuzz_fixed', 'jq_fuzz_execute']
decAddOp	174	47	27.01%	['jq_fuzz_fixed', 'jq_fuzz_execute']
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	80	48.19%	['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']
onigenc_egcb_is_break_position	53	22	41.50%	['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/lexer.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.c	[]	[]
/src/jq/vendor/oniguruma/src/ascii.c	[]	[]
/src/jq/vendor/decNumber/decNumber.c	['jq_fuzz_parse', 'jq_fuzz_load_file', 'jq_fuzz_parse_stream', 'jq_fuzz_parse_extended', 'jq_fuzz_compile', 'jq_fuzz_fixed', 'jq_fuzz_execute']	['jq_fuzz_parse', 'jq_fuzz_load_file', '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/vendor/oniguruma/src/unicode_fold1_key.c	[]	[]
/src/jq/vendor/decNumber/decContext.c	['jq_fuzz_parse', 'jq_fuzz_load_file', 'jq_fuzz_parse_stream', 'jq_fuzz_parse_extended', 'jq_fuzz_compile', 'jq_fuzz_fixed', 'jq_fuzz_execute']	['jq_fuzz_parse', 'jq_fuzz_load_file', 'jq_fuzz_parse_stream', 'jq_fuzz_parse_extended', 'jq_fuzz_compile', 'jq_fuzz_fixed', 'jq_fuzz_execute']
/src/jq/vendor/oniguruma/src/regcomp.c	[]	[]
/src/jq/src/jv_parse.c	['jq_fuzz_parse', 'jq_fuzz_load_file', 'jq_fuzz_parse_stream', 'jq_fuzz_parse_extended', 'jq_fuzz_compile', 'jq_fuzz_fixed', 'jq_fuzz_execute']	['jq_fuzz_parse', 'jq_fuzz_load_file', 'jq_fuzz_parse_stream', 'jq_fuzz_parse_extended', 'jq_fuzz_compile', 'jq_fuzz_fixed', 'jq_fuzz_execute']
/src/jq/src/libm.h	[]	[]
/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/vendor/oniguruma/src/regerror.c	[]	[]
/src/jq/tests/jq_fuzz_parse_extended.c	['jq_fuzz_parse_extended']	['jq_fuzz_parse_extended']
/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_alloc.c	['jq_fuzz_parse', 'jq_fuzz_load_file', 'jq_fuzz_parse_stream', 'jq_fuzz_parse_extended', 'jq_fuzz_compile', 'jq_fuzz_fixed', 'jq_fuzz_execute']	['jq_fuzz_parse', 'jq_fuzz_load_file', 'jq_fuzz_parse_stream', 'jq_fuzz_parse_extended', '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/locfile.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_parse', 'jq_fuzz_load_file', 'jq_fuzz_parse_stream', 'jq_fuzz_parse_extended', 'jq_fuzz_compile', 'jq_fuzz_fixed', 'jq_fuzz_execute']	['jq_fuzz_parse', 'jq_fuzz_load_file', 'jq_fuzz_parse_stream', 'jq_fuzz_parse_extended', 'jq_fuzz_compile', 'jq_fuzz_fixed', 'jq_fuzz_execute']
/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/jv_dtoa_tsd.c	['jq_fuzz_parse', 'jq_fuzz_load_file', '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_parse_stream.c	['jq_fuzz_parse_stream']	['jq_fuzz_parse_stream']
/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/parser.y	['jq_fuzz_compile', 'jq_fuzz_fixed', 'jq_fuzz_execute']	['jq_fuzz_compile', 'jq_fuzz_fixed', 'jq_fuzz_execute']
/src/jq/src/jv_dtoa.c	['jq_fuzz_parse', 'jq_fuzz_load_file', 'jq_fuzz_parse_stream', 'jq_fuzz_parse_extended', 'jq_fuzz_compile', 'jq_fuzz_fixed', 'jq_fuzz_execute']	['jq_fuzz_parse', 'jq_fuzz_load_file', '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/./tests/jq_fuzz_fixed.cpp	['jq_fuzz_fixed']	[]
/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/src/jv.h	['jq_fuzz_parse', 'jq_fuzz_load_file', 'jq_fuzz_parse_stream', 'jq_fuzz_parse_extended', 'jq_fuzz_compile', 'jq_fuzz_fixed', 'jq_fuzz_execute']	['jq_fuzz_parse', 'jq_fuzz_load_file', 'jq_fuzz_parse_stream', 'jq_fuzz_parse_extended', 'jq_fuzz_compile', 'jq_fuzz_fixed', 'jq_fuzz_execute']
/src/jq/./src/jv.h	['jq_fuzz_parse_extended', 'jq_fuzz_fixed', 'jq_fuzz_execute']	['jq_fuzz_parse', 'jq_fuzz_load_file', 'jq_fuzz_parse_stream', 'jq_fuzz_parse_extended', 'jq_fuzz_compile', 'jq_fuzz_fixed', 'jq_fuzz_execute']
/src/jq/vendor/oniguruma/src/unicode_unfold_key.c	[]	[]
/src/jq/vendor/oniguruma/src/st.c	[]	[]
/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/oniguruma/src/unicode_fold2_key.c	[]	[]
/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/src/jv_file.c	['jq_fuzz_load_file', 'jq_fuzz_compile', 'jq_fuzz_fixed', 'jq_fuzz_execute']	['jq_fuzz_load_file']
/src/jq/tests/jq_fuzz_parse.c	['jq_fuzz_parse']	['jq_fuzz_parse']
/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/vendor/oniguruma/src/utf8.c	[]	[]
/src/jq/tests/jq_fuzz_load_file.c	['jq_fuzz_load_file']	['jq_fuzz_load_file']
/src/jq/vendor/oniguruma/src/./unicode_property_data.c	[]	[]
/src/jq/vendor/oniguruma/src/regexec.c	[]	[]
/src/jq/vendor/oniguruma/src/regsyntax.c	[]	[]
/src/jq/vendor/oniguruma/src/unicode_fold3_key.c	[]	[]
/src/jq/./tests/jq_fuzz_execute.cpp	['jq_fuzz_execute']	[]
/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/regparse.c	[]	[]
/src/jq/src/jv_unicode.c	['jq_fuzz_parse', 'jq_fuzz_load_file', 'jq_fuzz_parse_stream', 'jq_fuzz_parse_extended', 'jq_fuzz_compile', 'jq_fuzz_fixed', 'jq_fuzz_execute']	['jq_fuzz_parse', 'jq_fuzz_load_file', 'jq_fuzz_parse_stream', 'jq_fuzz_parse_extended', 'jq_fuzz_compile', 'jq_fuzz_fixed', 'jq_fuzz_execute']
/src/jq/src/builtin.c	['jq_fuzz_compile', 'jq_fuzz_fixed', 'jq_fuzz_execute']	['jq_fuzz_compile', 'jq_fuzz_fixed', 'jq_fuzz_execute']

Directories in report

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