Fuzz introspector
For issues and ideas: https://github.com/ossf/fuzz-introspector/issues

Project functions overview

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 details

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 380 50.1%
gold [1:9] 8 1.05%
yellow [10:29] 3 0.39%
greenyellow [30:49] 0 0.0%
lawngreen 50+ 367 48.4%
All colors 758 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 209 jv_array_set call site: 00209 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 314 check_literal call site: 00314 check_literal
6 295 decSetSubnormal call site: 00295 decSetSubnormal
5 60 jv_load_file call site: 00060 jv_string_fmt
5 183 jv_array_set call site: 00183 jv_string
5 242 jv_parser_next call site: 00242 check_literal
5 323 parse_check_done call site: 00323 parser_reset
5 604 jvp_object_buckets call site: 00604 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

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 50.7%
gold [1:9] 8 1.10%
yellow [10:29] 7 0.97%
greenyellow [30:49] 4 0.55%
lawngreen 50+ 336 46.6%
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 282 scan call site: 00282 jv_number_value
32 152 jv_array_set call site: 00152 jv_array_slice
22 10 jvp_array_alloc call site: 00010 memory_exhausted
10 536 jvp_object_unshare call site: 00536 jvp_object_new
7 257 check_literal call site: 00257 check_literal
6 238 decSetSubnormal call site: 00238 decSetSubnormal
5 125 jv_array_set call site: 00125 jv_string
5 185 jv_parser_next call site: 00185 check_literal
5 266 parse_check_done call site: 00266 parser_reset
5 547 jvp_object_buckets call site: 00547 jvp_object_free
4 132 jvp_array_offset call site: 00132 jv_string
4 604 jvp_object_write call site: 00604 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_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 353 51.1%
gold [1:9] 14 2.02%
yellow [10:29] 1 0.14%
greenyellow [30:49] 1 0.14%
lawngreen 50+ 321 46.5%
All colors 690 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
125 506 scan call site: 00506 jv_object_set
22 2 jv_parser_new call site: 00002 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
4 649 jv_string_vfmt call site: 00649 jv_array_append
3 164 jvp_array_slice call site: 00164 jv_array_get
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
96
Functions that are reachable but not covered
84
Reachable functions
180
Percentage of reachable functions covered
53.33%
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 72
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 239 24.2%
gold [1:9] 41 4.16%
yellow [10:29] 38 3.85%
greenyellow [30:49] 3 0.30%
lawngreen 50+ 664 67.4%
All colors 985 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 817 jvp_dtoa call site: 00817 pow5mult
30 398 diff call site: 00398 bigcomp
22 9 jvp_array_alloc call site: 00009 memory_exhausted
19 728 put_str call site: 00728 jv_string_append_buf
10 433 quorem call site: 00433 multadd
10 535 jvp_object_unshare call site: 00535 jvp_object_new
8 358 jvp_strtod call site: 00358 s2b
6 237 decSetSubnormal call site: 00237 decSetSubnormal
6 367 Balloc call site: 00367 d2b
5 124 jv_array_set call site: 00124 jv_string
5 546 jvp_object_buckets call site: 00546 jvp_object_free
5 750 jv_dump_term call site: 00750 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 1383 45.4%
gold [1:9] 129 4.23%
yellow [10:29] 61 2.00%
greenyellow [30:49] 20 0.65%
lawngreen 50+ 1453 47.7%
All colors 3046 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 1966 gen_param call site: 01966 gen_binop
93 677 quorem call site: 00677 parse_token
92 300 yy_push_state call site: 00300 jv_parse_sized
74 2586 process_dependencies call site: 02586 load_library
48 2129 gen_foreach call site: 02129 gen_lambda
48 2210 gen_object_matcher call site: 02210 check_object_key
43 2661 block_has_only_binders_and_imports call site: 02661 process_dependencies
39 2261 gen_dictpair call site: 02261 check_object_key
38 1515 jvp_dtoa call site: 01515 pow5mult
38 1872 gen_error call site: 01872 gen_update
29 1932 gen_import call site: 01932 gen_function
28 128 jvp_array_free call site: 00128 jv_array_slice

Runtime coverage analysis

Covered functions
381
Functions that are reachable but not covered
104
Reachable functions
481
Percentage of reachable functions covered
78.38%
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 1411 40.1%
gold [1:9] 88 2.50%
yellow [10:29] 36 1.02%
greenyellow [30:49] 31 0.88%
lawngreen 50+ 1945 55.3%
All colors 3511 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 1969 gen_param call site: 01969 gen_binop
93 381 yy_push_state call site: 00381 jv_parse_sized
82 2580 process_dependencies call site: 02580 load_library
70 759 quorem call site: 00759 jv_array_slice
57 2263 gen_dictpair call site: 02263 check_object_key
54 3025 jq_next call site: 03025 dump_operation
48 2212 gen_object_matcher call site: 02212 check_object_key
47 2132 gen_foreach call site: 02132 gen_lambda
46 1867 binop_greatereq call site: 01867 gen_update
43 2663 block_has_only_binders_and_imports call site: 02663 process_dependencies
38 1518 jvp_dtoa call site: 01518 pow5mult
29 1935 gen_import call site: 01935 gen_function

Runtime coverage analysis

Covered functions
700
Functions that are reachable but not covered
93
Reachable functions
501
Percentage of reachable functions covered
81.44%
NB: The sum of covered functions and functions that are reachable but not covered need not be equal to Reachable functions . This is because the reachability analysis is an approximation and thus at runtime some functions may be covered that are not included in the reachability analysis. This is a limitation of our static analysis capabilities.
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 1273 36.2%
gold [1:9] 89 2.53%
yellow [10:29] 18 0.51%
greenyellow [30:49] 15 0.42%
lawngreen 50+ 2117 60.2%
All colors 3512 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 1969 gen_param call site: 01969 gen_binop
92 382 yy_push_state call site: 00382 jv_parse_sized
74 2589 process_dependencies call site: 02589 load_library
70 759 quorem call site: 00759 jv_array_slice
52 3028 jq_next call site: 03028 dump_operation
48 2132 gen_foreach call site: 02132 gen_lambda
48 2213 gen_object_matcher call site: 02213 check_object_key
43 2664 block_has_only_binders_and_imports call site: 02664 process_dependencies
39 2264 gen_dictpair call site: 02264 check_object_key
38 1518 jvp_dtoa call site: 01518 pow5mult
38 1875 gen_error call site: 01875 gen_update
29 1935 gen_import call site: 01935 gen_function

Runtime coverage analysis

Covered functions
984
Functions that are reachable but not covered
85
Reachable functions
501
Percentage of reachable functions covered
83.03%
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

Analyses and suggestions

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 616 0 6169 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'] 18 0 40 3 2 212 0 1552 97
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 1945 178 53 177 0 1292 64
jq_util_input_next_input_cb /src/jq/src/util.c 2 ['N/A', 'N/A'] 17 0 25 3 2 196 0 1378 54
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
67.0%
939 / 1400
Cyclomatic complexity statically reachable by fuzzers
81.0%
8771 / 10784

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

Fuzz engine guidance

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', '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_object_matcher', 'gen_foreach', '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']

Files and Directories in report

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/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/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.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_fold3_key.c [] []
/src/jq/vendor/oniguruma/src/unicode_fold2_key.c [] []
/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/unicode.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/tests/jq_fuzz_compile.c ['jq_fuzz_compile'] ['jq_fuzz_compile']
/src/jq/vendor/oniguruma/src/regsyntax.c [] []
/src/jq/tests/jq_fuzz_parse.c ['jq_fuzz_parse'] ['jq_fuzz_parse']
/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/unicode_unfold_key.c [] []
/src/jq/tests/jq_fuzz_load_file.c ['jq_fuzz_load_file'] ['jq_fuzz_load_file']
/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/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/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/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/regcomp.c [] []
/src/jq/vendor/oniguruma/src/unicode_fold1_key.c [] []
/src/jq/vendor/oniguruma/src/./unicode_property_data.c [] []
/src/jq/tests/jq_fuzz_parse_extended.c ['jq_fuzz_parse_extended'] ['jq_fuzz_parse_extended']
/src/jq/vendor/oniguruma/src/st.c [] []
/src/jq/vendor/oniguruma/src/regenc.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/builtin.c ['jq_fuzz_compile', 'jq_fuzz_fixed', 'jq_fuzz_execute'] ['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/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/regexec.c [] []
/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/vendor/oniguruma/src/ascii.c [] []
/src/jq/tests/jq_fuzz_parse_stream.c ['jq_fuzz_parse_stream'] ['jq_fuzz_parse_stream']
/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/libm.h [] []
/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_execute.cpp ['jq_fuzz_execute'] []
/src/jq/vendor/oniguruma/src/regerror.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/utf8.c [] []
/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/execute.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/./tests/jq_fuzz_fixed.cpp ['jq_fuzz_fixed'] []
/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/src/compile.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/locfile.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/./src/
/src/jq/vendor/oniguruma/src/./
/src/jq/src/
/src/jq/tests/
/src/jq/./tests/
/src/jq/vendor/oniguruma/src/