High level conclusions

Fuzzers reach 72.30% code coverage.

Fuzzers reach 27.22% of cyclomatic complexity.

Fuzzers reach 32.23% of all functions.

Reachability and coverage overview

Functions statically reachable by fuzzers

461 / 1430

Cyclomatic complexity statically reachable by fuzzers

2991 / 10985

Runtime code coverage of functions

1034 / 1430

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	391	50.7%
gold	[1:9]	9	1.16%
yellow	[10:29]	1	0.12%
greenyellow	[30:49]	1	0.12%
lawngreen	50+	369	47.8%
All colors	771	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	341	scan	call site: 00341	jv_number_value
32	206	jv_array_set	call site: 00206	jv_array_slice
22	12	jv_string_vfmt	call site: 00012	memory_exhausted
10	595	jvp_object_unshare	call site: 00595	jvp_object_new
7	311	check_literal	call site: 00311	check_literal
7	622	jvp_hash_seed_init	call site: 00622	open
6	292	decSetSubnormal	call site: 00292	decSetSubnormal
5	67	jv_load_file	call site: 00067	jv_string_fmt
5	180	jv_array_set	call site: 00180	jv_string
5	239	jv_parser_next	call site: 00239	check_literal
5	320	parse_check_done	call site: 00320	parser_reset
5	606	jvp_object_buckets	call site: 00606	jv_free

Runtime coverage analysis

Covered functions

115

Functions that are reachable but not covered

92

Reachable functions

207

Percentage of reachable functions covered

55.56%

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_unicode.h	1
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	374	51.3%
gold	[1:9]	9	1.23%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	9	1.23%
lawngreen	50+	337	46.2%
All colors	729	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	279	scan	call site: 00279	jv_number_value
32	144	jv_array_set	call site: 00144	jv_array_slice
22	10	jvp_array_alloc	call site: 00010	memory_exhausted
10	533	jvp_object_unshare	call site: 00533	jvp_object_new
7	249	check_literal	call site: 00249	check_literal
7	560	jvp_hash_seed_init	call site: 00560	open
6	230	decSetSubnormal	call site: 00230	decSetSubnormal
5	177	jv_parser_next	call site: 00177	check_literal
5	258	parse_check_done	call site: 00258	parser_reset
5	544	jvp_object_buckets	call site: 00544	jv_free
4	94	jv_array_set	call site: 00094	jv_string
4	124	jvp_array_offset	call site: 00124	jv_string

Runtime coverage analysis

Covered functions

112

Functions that are reachable but not covered

79

Reachable functions

191

Percentage of reachable functions covered

58.64%

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.h	1
src/jv_unicode.c	4
src/jv_unicode.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	366	52.4%
gold	[1:9]	10	1.43%
yellow	[10:29]	2	0.28%
greenyellow	[30:49]	1	0.14%
lawngreen	50+	319	45.7%
All colors	698	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
136	503	scan	call site: 00503	jv_object_set
134	305	jv_number_value	call site: 00305	jvp_literal_number_to_double
22	2	jv_parser_new	call site: 00002	memory_exhausted
12	247	check_literal	call site: 00247	check_literal
6	92	jv_array_set	call site: 00092	jv_string
6	228	decSetSubnormal	call site: 00228	decSetSubnormal
5	175	jv_parser_next	call site: 00175	check_literal
4	122	jvp_array_offset	call site: 00122	jv_string
4	657	jv_string_vfmt	call site: 00657	jv_array_append
3	156	jvp_array_slice	call site: 00156	jv_array_get
3	265	parser_reset	call site: 00265	jv_free
2	109	jv_string_sized	call site: 00109	jv_string

Runtime coverage analysis

Covered functions

93

Functions that are reachable but not covered

93

Reachable functions

186

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.

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.h	1
src/jv_unicode.c	4
src/jv_unicode.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	253	25.3%
gold	[1:9]	54	5.4%
yellow	[10:29]	23	2.3%
greenyellow	[30:49]	5	0.5%
lawngreen	50+	665	66.5%
All colors	1000	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	833	jvp_dtoa	call site: 00833	pow5mult
30	395	diff	call site: 00395	bigcomp
23	737	put_str	call site: 00737	jv_string_append_buf
22	9	jvp_array_alloc	call site: 00009	memory_exhausted
10	430	quorem	call site: 00430	multadd
10	532	jvp_object_unshare	call site: 00532	jvp_object_new
8	355	jvp_strtod	call site: 00355	s2b
7	559	jvp_hash_seed_init	call site: 00559	open
6	229	decSetSubnormal	call site: 00229	decSetSubnormal
6	364	Balloc	call site: 00364	d2b
5	543	jvp_object_buckets	call site: 00543	jv_free
5	764	jv_dump_term	call site: 00764	jvp_dump_string

Runtime coverage analysis

Covered functions

182

Functions that are reachable but not covered

47

Reachable functions

227

Percentage of reachable functions covered

79.3%

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.h	1
src/jv_unicode.c	4
src/jv_unicode.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/util.h	1
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	1358	43.5%
gold	[1:9]	61	1.95%
yellow	[10:29]	21	0.67%
greenyellow	[30:49]	10	0.32%
lawngreen	50+	1668	53.4%
All colors	3118	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	2025	gen_param	call site: 02025	gen_binop
92	671	quorem	call site: 00671	parse_token
86	2645	process_dependencies	call site: 02645	load_library
83	306	yy_pop_state	call site: 00306	jv_parse_sized
48	2188	gen_foreach	call site: 02188	gen_lambda
48	2270	gen_object_matcher	call site: 02270	check_object_key
43	2732	block_has_only_binders_and_imports	call site: 02732	process_dependencies
40	2321	gen_dictpair	call site: 02321	check_object_key
38	1547	jvp_dtoa	call site: 01547	pow5mult
38	1931	gen_error	call site: 01931	gen_update
28	518	tokenadd	call site: 00518	stream_token
27	131	jv_free	call site: 00131	jv_array_slice

Runtime coverage analysis

Covered functions

394

Functions that are reachable but not covered

100

Reachable functions

490

Percentage of reachable functions covered

79.59%

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_unicode.h	1
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/util.h	1
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	1461	40.8%
gold	[1:9]	99	2.76%
yellow	[10:29]	35	0.97%
greenyellow	[30:49]	17	0.47%
lawngreen	50+	1963	54.9%
All colors	3575	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	2028	gen_param	call site: 02028	gen_binop
93	2641	process_dependencies	call site: 02641	load_library
83	399	yy_pop_state	call site: 00399	jv_parse_sized
69	764	quorem	call site: 00764	jv_array_slice
58	2324	gen_dictpair	call site: 02324	check_object_key
53	3100	jq_next	call site: 03100	dump_operation
48	2191	gen_foreach	call site: 02191	gen_lambda
48	2273	gen_object_matcher	call site: 02273	check_object_key
44	1928	binop_greatereq	call site: 01928	gen_update
43	2735	block_has_only_binders_and_imports	call site: 02735	process_dependencies
38	1550	jvp_dtoa	call site: 01550	pow5mult
27	612	scan	call site: 00612	jv_number_value

Runtime coverage analysis

Covered functions

727

Functions that are reachable but not covered

99

Reachable functions

509

Percentage of reachable functions covered

80.55%

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/jv_unicode.h	1
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/util.h	1
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	1339	37.4%
gold	[1:9]	58	1.62%
yellow	[10:29]	11	0.30%
greenyellow	[30:49]	7	0.19%
lawngreen	50+	2160	60.4%
All colors	3575	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	2028	gen_param	call site: 02028	gen_binop
86	2648	process_dependencies	call site: 02648	load_library
83	399	yy_pop_state	call site: 00399	jv_parse_sized
69	764	quorem	call site: 00764	jv_array_slice
51	3102	jq_next	call site: 03102	dump_operation
48	2191	gen_foreach	call site: 02191	gen_lambda
48	2273	gen_object_matcher	call site: 02273	check_object_key
43	2735	block_has_only_binders_and_imports	call site: 02735	process_dependencies
40	2324	gen_dictpair	call site: 02324	check_object_key
38	1550	jvp_dtoa	call site: 01550	pow5mult
38	1934	gen_error	call site: 01934	gen_update
27	612	scan	call site: 00612	jv_number_value

Runtime coverage analysis

Covered functions

1008

Functions that are reachable but not covered

89

Reachable functions

509

Percentage of reachable functions covered

82.51%

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/jv_unicode.h	1
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/util.h	1
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	629	0	6223	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
f_fromdateiso8601	/src/jq/src/builtin.c	3	['N/A', 'size_t', 'N/A']	13	0	132	8	4	70	0	279	128
f_delpaths	/src/jq/src/builtin.c	5	['N/A', 'size_t', 'N/A', 'size_t', 'N/A']	19	0	40	3	2	224	0	1599	106
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
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	190	0	1344	64
jq_util_input_next_input_cb	/src/jq/src/util.c	2	['N/A', 'N/A']	17	0	25	3	2	202	0	1389	55

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

Functions statically reachable by fuzzers

964 / 1430

Cyclomatic complexity statically reachable by fuzzers

8904 / 10985

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', 'jvp_hash_seed_init', 'decSetSubnormal', 'jv_load_file', 'jv_parser_next']

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', 'jvp_hash_seed_init', '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=['scan', 'jv_number_value', 'jv_parser_new', 'check_literal', 'jv_array_set', 'decSetSubnormal', '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', 'put_str', 'jvp_array_alloc', 'quorem', 'jvp_object_unshare', 'jvp_strtod', 'jvp_hash_seed_init', 'decSetSubnormal', 'Balloc']

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', 'process_dependencies', 'yy_pop_state', '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', 'process_dependencies', 'yy_pop_state', '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', 'process_dependencies', 'yy_pop_state', '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_fixed', 'jq_fuzz_load_file', 'jq_fuzz_parse', 'jq_fuzz_compile', 'jq_fuzz_parse_extended', 'jq_fuzz_execute']
decApplyRound	94	36	38.29%	['jq_fuzz_parse_stream', 'jq_fuzz_fixed', 'jq_fuzz_load_file', 'jq_fuzz_parse', 'jq_fuzz_compile', 'jq_fuzz_parse_extended', 'jq_fuzz_execute']
jvp_dtoa	273	120	43.95%	['jq_fuzz_compile', 'jq_fuzz_fixed', 'jq_fuzz_parse_extended', 'jq_fuzz_execute']
yy_get_next_buffer	90	19	21.11%	['jq_fuzz_compile', 'jq_fuzz_fixed', 'jq_fuzz_execute']
decCompareOp	91	23	25.27%	['jq_fuzz_compile', 'jq_fuzz_fixed', 'jq_fuzz_execute']
jv_delpaths	35	19	54.28%	['jq_fuzz_fixed', 'jq_fuzz_execute']
decAddOp	174	45	25.86%	['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	84	50.60%	['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/lexer.l	['jq_fuzz_compile', 'jq_fuzz_fixed', 'jq_fuzz_execute']	['jq_fuzz_compile', 'jq_fuzz_fixed', 'jq_fuzz_execute']
/src/jq/tests/jq_fuzz_parse.c	['jq_fuzz_parse']	['jq_fuzz_parse']
/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/unicode_unfold_key.c	[]	[]
/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/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/builtin.c	['jq_fuzz_compile', 'jq_fuzz_fixed', 'jq_fuzz_execute']	['jq_fuzz_compile', 'jq_fuzz_fixed', '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/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']
/src/jq/vendor/oniguruma/src/regexec.c	[]	[]
/src/jq/tests/jq_fuzz_parse_stream.c	['jq_fuzz_parse_stream']	['jq_fuzz_parse_stream']
/src/jq/src/libm.h	[]	[]
/src/jq/vendor/oniguruma/src/unicode_fold2_key.c	[]	[]
/src/jq/tests/jq_fuzz_load_file.c	['jq_fuzz_load_file']	['jq_fuzz_load_file']
/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/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_unicode.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/vendor/oniguruma/src/unicode.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/vendor/oniguruma/src/regcomp.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/regenc.c	[]	[]
/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/vendor/oniguruma/src/st.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/./tests/jq_fuzz_execute.cpp	['jq_fuzz_execute']	[]
/src/jq/tests/jq_fuzz_parse_extended.c	['jq_fuzz_parse_extended']	['jq_fuzz_parse_extended']
/src/jq/vendor/oniguruma/src/./unicode_property_data.c	[]	[]
/src/jq/vendor/oniguruma/src/regsyntax.c	[]	[]
/src/jq/src/iso8601.c	[]	[]
/src/jq/./tests/jq_fuzz_fixed.cpp	['jq_fuzz_fixed']	[]
/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/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/src/parser.c	['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/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/vendor/oniguruma/src/unicode_fold1_key.c	[]	[]
/src/jq/vendor/oniguruma/src/ascii.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/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/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/locfile.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/src/util.h	['jq_fuzz_parse_extended', 'jq_fuzz_compile', 'jq_fuzz_fixed', 'jq_fuzz_execute']	['jq_fuzz_parse_extended', 'jq_fuzz_compile']
/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/unicode_fold3_key.c	[]	[]
/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/regparse.c	[]	[]
/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_compile.c	['jq_fuzz_compile']	['jq_fuzz_compile']
/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']

Directories in report

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