High level conclusions

Fuzzer yaml_generic is blocked:

The runtime code coverage of yaml_generic covers 10.0% of its statically reachable code. This means there is some place that blocks the fuzzer to continue exploring more code at run time.

Fuzzer jsonrpc_registry is blocked:

The runtime code coverage of jsonrpc_registry covers 4.347% of its statically reachable code. This means there is some place that blocks the fuzzer to continue exploring more code at run time.

Fuzzer msgpack_roundtrip_int is blocked:

The runtime code coverage of msgpack_roundtrip_int covers 2.631% of its statically reachable code. This means there is some place that blocks the fuzzer to continue exploring more code at run time.

Fuzzer json_jmespath is blocked:

The runtime code coverage of json_jmespath covers 8.333% of its statically reachable code. This means there is some place that blocks the fuzzer to continue exploring more code at run time.

Fuzzer json_prettify is blocked:

The runtime code coverage of json_prettify covers 25.0% of its statically reachable code. This means there is some place that blocks the fuzzer to continue exploring more code at run time.

Fuzzer msgpack_roundtrip_floating is blocked:

The runtime code coverage of msgpack_roundtrip_floating covers 2.631% of its statically reachable code. This means there is some place that blocks the fuzzer to continue exploring more code at run time.

Fuzzer cbor_roundtrip_floating is blocked:

The runtime code coverage of cbor_roundtrip_floating covers 2.631% of its statically reachable code. This means there is some place that blocks the fuzzer to continue exploring more code at run time.

Fuzzer json_generic is blocked:

The runtime code coverage of json_generic covers 12.5% of its statically reachable code. This means there is some place that blocks the fuzzer to continue exploring more code at run time.

Fuzzer repe_registry is blocked:

The runtime code coverage of repe_registry covers 3.225% of its statically reachable code. This means there is some place that blocks the fuzzer to continue exploring more code at run time.

Fuzzer json_roundtrip_int is blocked:

The runtime code coverage of json_roundtrip_int covers 2.631% of its statically reachable code. This means there is some place that blocks the fuzzer to continue exploring more code at run time.

Fuzzer json_roundtrip_floating is blocked:

The runtime code coverage of json_roundtrip_floating covers 2.631% of its statically reachable code. This means there is some place that blocks the fuzzer to continue exploring more code at run time.

Fuzzer json_minify is blocked:

The runtime code coverage of json_minify covers 25.0% of its statically reachable code. This means there is some place that blocks the fuzzer to continue exploring more code at run time.

Fuzzer cbor_roundtrip_int is blocked:

The runtime code coverage of cbor_roundtrip_int covers 2.631% of its statically reachable code. This means there is some place that blocks the fuzzer to continue exploring more code at run time.

Fuzzer jsonb_reflection is blocked:

The runtime code coverage of jsonb_reflection covers 20.0% of its statically reachable code. This means there is some place that blocks the fuzzer to continue exploring more code at run time.

Fuzzer json_with_comments is blocked:

The runtime code coverage of json_with_comments covers 25.0% of its statically reachable code. This means there is some place that blocks the fuzzer to continue exploring more code at run time.

Fuzzer msgpack_roundtrip_string is blocked:

The runtime code coverage of msgpack_roundtrip_string covers 2.631% of its statically reachable code. This means there is some place that blocks the fuzzer to continue exploring more code at run time.

Fuzzer json_roundtrip_string is blocked:

The runtime code coverage of json_roundtrip_string covers 2.631% of its statically reachable code. This means there is some place that blocks the fuzzer to continue exploring more code at run time.

Fuzzer cbor_roundtrip_string is blocked:

The runtime code coverage of cbor_roundtrip_string covers 2.631% of its statically reachable code. This means there is some place that blocks the fuzzer to continue exploring more code at run time.

Fuzzer cbor_reflection is blocked:

The runtime code coverage of cbor_reflection covers 20.0% of its statically reachable code. This means there is some place that blocks the fuzzer to continue exploring more code at run time.

Fuzzer binary_reflection is blocked:

The runtime code coverage of binary_reflection covers 8.333% of its statically reachable code. This means there is some place that blocks the fuzzer to continue exploring more code at run time.

Fuzzer json_reflection is blocked:

The runtime code coverage of json_reflection covers 16.66% of its statically reachable code. This means there is some place that blocks the fuzzer to continue exploring more code at run time.

Fuzzers reach 0.594% of cyclomatic complexity.

Fuzzers reach 0.978% of all functions.

Reachability and coverage overview

Functions statically reachable by fuzzers

35 / 3577

Cyclomatic complexity statically reachable by fuzzers

70 / 11765

Runtime code coverage of functions

3 / 3577

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

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	0	0.0%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	4	100.%
All colors	4	100

Runtime coverage analysis

Covered functions

49

Functions that are reachable but not covered

2

Reachable functions

3

Percentage of reachable functions covered

33.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.

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
fuzzing/msgpack_reflection.cpp	3

Fuzzer: json_reflection

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	1	16.6%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	5	83.3%
All colors	6	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
1	0	EP	call site: 00000

Runtime coverage analysis

Covered functions

224

Functions that are reachable but not covered

5

Reachable functions

6

Percentage of reachable functions covered

16.67%

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
fuzzing/json_reflection.cpp	4

Fuzzer: binary_reflection

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	7	58.3%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	5	41.6%
All colors	12	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
7	2	LLVMFuzzerTestOneInput	call site: 00002	glz::get_size

Runtime coverage analysis

Covered functions

226

Functions that are reachable but not covered

11

Reachable functions

12

Percentage of reachable functions covered

8.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.

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
fuzzing/binary_reflection.cpp	4
include/glaze/beve/beve_to_json.hpp	4
include/glaze/core/streaming_state.hpp	2
include/glaze/core/common.hpp	1

Fuzzer: cbor_reflection

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	7	58.3%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	5	41.6%
All colors	12	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
7	2	LLVMFuzzerTestOneInput	call site: 00002	glz::get_size

Runtime coverage analysis

Covered functions

178

Functions that are reachable but not covered

4

Reachable functions

5

Percentage of reachable functions covered

20.0%

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

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

Function name	source code lines	source lines hit	percentage hit

Files reached

filename	functions hit
fuzzing/cbor_reflection.cpp	4
include/glaze/cbor/cbor_to_json.hpp	4
include/glaze/core/streaming_state.hpp	2
include/glaze/core/common.hpp	1

Fuzzer: cbor_roundtrip_string

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	15	88.2%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	2	11.7%
All colors	17	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
15	1	LLVMFuzzerTestOneInput	call site: 00001	glz::get_size

Runtime coverage analysis

Covered functions

52

Functions that are reachable but not covered

37

Reachable functions

38

Percentage of reachable functions covered

2.63%

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

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

Function name	source code lines	source lines hit	percentage hit

Files reached

filename	functions hit
fuzzing/cbor_roundtrip_string.cpp	2
fuzzing/msgpack_roundtrip_string.cpp	4
include/glaze/msgpack/write.hpp	3
include/glaze/core/write.hpp	4
include/glaze/core/streaming_state.hpp	1
include/glaze/core/common.hpp	1

Fuzzer: csv_parsing

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	0	0.0%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	3	100.%
All colors	3	100

Runtime coverage analysis

Covered functions

192

Functions that are reachable but not covered

2

Reachable functions

3

Percentage of reachable functions covered

33.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.

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
fuzzing/csv_parsing.cpp	3

Fuzzer: json_roundtrip_string

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	15	88.2%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	2	11.7%
All colors	17	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
15	1	LLVMFuzzerTestOneInput	call site: 00001	glz::get_size

Runtime coverage analysis

Covered functions

51

Functions that are reachable but not covered

37

Reachable functions

38

Percentage of reachable functions covered

2.63%

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

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

Function name	source code lines	source lines hit	percentage hit

Files reached

filename	functions hit
fuzzing/json_roundtrip_string.cpp	2
fuzzing/msgpack_roundtrip_string.cpp	4
include/glaze/msgpack/write.hpp	3
include/glaze/core/write.hpp	4
include/glaze/core/streaming_state.hpp	1
include/glaze/core/common.hpp	1

Fuzzer: msgpack_roundtrip_string

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	15	88.2%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	2	11.7%
All colors	17	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
15	1	LLVMFuzzerTestOneInput	call site: 00001	glz::get_size

Runtime coverage analysis

Covered functions

49

Functions that are reachable but not covered

37

Reachable functions

38

Percentage of reachable functions covered

2.63%

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

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

Function name	source code lines	source lines hit	percentage hit

Files reached

filename	functions hit
fuzzing/msgpack_roundtrip_string.cpp	6
include/glaze/msgpack/write.hpp	3
include/glaze/core/write.hpp	4
include/glaze/core/streaming_state.hpp	1
include/glaze/core/common.hpp	1

Fuzzer: json_with_comments

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	0	0.0%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	4	100.%
All colors	4	100

Runtime coverage analysis

Covered functions

183

Functions that are reachable but not covered

3

Reachable functions

4

Percentage of reachable functions covered

25.0%

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

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

Function name	source code lines	source lines hit	percentage hit

Files reached

filename	functions hit
fuzzing/json_with_comments.cpp	4

Fuzzer: jsonb_reflection

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	8	66.6%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	4	33.3%
All colors	12	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
8	2	LLVMFuzzerTestOneInput	call site: 00002	glz::get_size

Runtime coverage analysis

Covered functions

338

Functions that are reachable but not covered

4

Reachable functions

5

Percentage of reachable functions covered

20.0%

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

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

Function name	source code lines	source lines hit	percentage hit

Files reached

filename	functions hit
fuzzing/jsonb_reflection.cpp	4
include/glaze/jsonb/jsonb_to_json.hpp	4
include/glaze/core/streaming_state.hpp	2
include/glaze/core/common.hpp	1

Fuzzer: cbor_roundtrip_int

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	15	62.5%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	9	37.5%
All colors	24	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
15	1	LLVMFuzzerTestOneInput	call site: 00001	glz::get_size

Runtime coverage analysis

Covered functions

255

Functions that are reachable but not covered

37

Reachable functions

38

Percentage of reachable functions covered

2.63%

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

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

Function name	source code lines	source lines hit	percentage hit

Files reached

filename	functions hit
fuzzing/cbor_roundtrip_int.cpp	2
fuzzing/msgpack_roundtrip_string.cpp	4
include/glaze/msgpack/write.hpp	3
include/glaze/core/write.hpp	4
include/glaze/core/streaming_state.hpp	1
include/glaze/core/common.hpp	1

Fuzzer: json_minify

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	1	20.0%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	4	80.0%
All colors	5	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
1	1	LLVMFuzzerTestOneInput	call site: 00001

Runtime coverage analysis

Covered functions

18

Functions that are reachable but not covered

3

Reachable functions

4

Percentage of reachable functions covered

25.0%

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

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

Function name	source code lines	source lines hit	percentage hit

Files reached

filename	functions hit
fuzzing/json_minify.cpp	3
include/glaze/json/minify.hpp	1

Fuzzer: json_roundtrip_floating

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	15	83.3%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	3	16.6%
All colors	18	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
15	1	LLVMFuzzerTestOneInput	call site: 00001	glz::get_size

Runtime coverage analysis

Covered functions

149

Functions that are reachable but not covered

37

Reachable functions

38

Percentage of reachable functions covered

2.63%

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

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

Function name	source code lines	source lines hit	percentage hit

Files reached

filename	functions hit
fuzzing/json_roundtrip_floating.cpp	2
fuzzing/msgpack_roundtrip_string.cpp	4
include/glaze/msgpack/write.hpp	3
include/glaze/core/write.hpp	4
include/glaze/core/streaming_state.hpp	1
include/glaze/core/common.hpp	1

Fuzzer: json_roundtrip_int

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	15	62.5%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	9	37.5%
All colors	24	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
15	1	LLVMFuzzerTestOneInput	call site: 00001	glz::get_size

Runtime coverage analysis

Covered functions

427

Functions that are reachable but not covered

37

Reachable functions

38

Percentage of reachable functions covered

2.63%

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

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

Function name	source code lines	source lines hit	percentage hit

Files reached

filename	functions hit
fuzzing/json_roundtrip_int.cpp	2
fuzzing/msgpack_roundtrip_string.cpp	4
include/glaze/msgpack/write.hpp	3
include/glaze/core/write.hpp	4
include/glaze/core/streaming_state.hpp	1
include/glaze/core/common.hpp	1

Fuzzer: repe_registry

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	56	70.8%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	23	29.1%
All colors	79	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
19	2	LLVMFuzzerTestOneInput	call site: 00002
16	22	LLVMFuzzerTestOneInput	call site: 00022	exact_buffer
16	53	LLVMFuzzerTestOneInput	call site: 00053
4	41	LLVMFuzzerTestOneInput	call site: 00041
1	0	EP	call site: 00000

Runtime coverage analysis

Covered functions

708

Functions that are reachable but not covered

30

Reachable functions

31

Percentage of reachable functions covered

3.23%

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
fuzzing/repe_registry.cpp	16
tests/json_test/lazy_test.cpp	7
tests/csv_test/csv_test.cpp	1
tests/cbor_test/cbor_test.cpp	2
tests/json_test/json_test.cpp	1
fuzzing/jsonrpc_registry.cpp	6
tests/networking_tests/repe_plugin_test/repe_plugin_test.cpp	4
include/glaze/rpc/repe/plugin_helper.hpp	4

Fuzzer: json_generic

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	4	33.3%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	8	66.6%
All colors	12	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
4	4	LLVMFuzzerTestOneInput	call site: 00004	glz::convert_from_generic

Runtime coverage analysis

Covered functions

389

Functions that are reachable but not covered

7

Reachable functions

8

Percentage of reachable functions covered

12.5%

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
fuzzing/json_generic.cpp	5
include/glaze/json/generic.hpp	2
include/glaze/beve/lazy.hpp	1

Fuzzer: cbor_roundtrip_floating

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	15	83.3%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	3	16.6%
All colors	18	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
15	1	LLVMFuzzerTestOneInput	call site: 00001	glz::get_size

Runtime coverage analysis

Covered functions

84

Functions that are reachable but not covered

37

Reachable functions

38

Percentage of reachable functions covered

2.63%

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

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

Function name	source code lines	source lines hit	percentage hit

Files reached

filename	functions hit
fuzzing/cbor_roundtrip_floating.cpp	2
fuzzing/msgpack_roundtrip_string.cpp	4
include/glaze/msgpack/write.hpp	3
include/glaze/core/write.hpp	4
include/glaze/core/streaming_state.hpp	1
include/glaze/core/common.hpp	1

Fuzzer: msgpack_roundtrip_floating

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	15	83.3%
gold	[1:9]	0	0.0%
yellow	[10:29]	1	5.55%
greenyellow	[30:49]	1	5.55%
lawngreen	50+	1	5.55%
All colors	18	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
15	1	LLVMFuzzerTestOneInput	call site: 00001	glz::get_size

Runtime coverage analysis

Covered functions

68

Functions that are reachable but not covered

37

Reachable functions

38

Percentage of reachable functions covered

2.63%

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

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

Function name	source code lines	source lines hit	percentage hit

Files reached

filename	functions hit
fuzzing/msgpack_roundtrip_floating.cpp	2
fuzzing/msgpack_roundtrip_string.cpp	4
include/glaze/msgpack/write.hpp	3
include/glaze/core/write.hpp	4
include/glaze/core/streaming_state.hpp	1
include/glaze/core/common.hpp	1

Fuzzer: json_prettify

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	1	20.0%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	4	80.0%
All colors	5	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
1	1	LLVMFuzzerTestOneInput	call site: 00001

Runtime coverage analysis

Covered functions

17

Functions that are reachable but not covered

3

Reachable functions

4

Percentage of reachable functions covered

25.0%

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

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

Function name	source code lines	source lines hit	percentage hit

Files reached

filename	functions hit
fuzzing/json_prettify.cpp	3
include/glaze/json/prettify.hpp	1

Fuzzer: json_jmespath

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	21	84.0%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	4	16.0%
All colors	25	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
21	2	LLVMFuzzerTestOneInput	call site: 00002

Runtime coverage analysis

Covered functions

112

Functions that are reachable but not covered

11

Reachable functions

12

Percentage of reachable functions covered

8.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.

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
fuzzing/json_jmespath.cpp	11
tests/cbor_test/cbor_test.cpp	2

Fuzzer: msgpack_roundtrip_int

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	15	62.5%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	9	37.5%
All colors	24	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
15	1	LLVMFuzzerTestOneInput	call site: 00001	glz::get_size

Runtime coverage analysis

Covered functions

197

Functions that are reachable but not covered

37

Reachable functions

38

Percentage of reachable functions covered

2.63%

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

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

Function name	source code lines	source lines hit	percentage hit

Files reached

filename	functions hit
fuzzing/msgpack_roundtrip_int.cpp	2
fuzzing/msgpack_roundtrip_string.cpp	4
include/glaze/msgpack/write.hpp	3
include/glaze/core/write.hpp	4
include/glaze/core/streaming_state.hpp	1
include/glaze/core/common.hpp	1

Fuzzer: jsonrpc_registry

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	36	72.0%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	14	28.0%
All colors	50	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
19	2	LLVMFuzzerTestOneInput	call site: 00002
16	22	LLVMFuzzerTestOneInput	call site: 00022	exact_buffer
1	0	EP	call site: 00000

Runtime coverage analysis

Covered functions

951

Functions that are reachable but not covered

22

Reachable functions

23

Percentage of reachable functions covered

4.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.

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
fuzzing/jsonrpc_registry.cpp	9
tests/json_test/lazy_test.cpp	7
tests/csv_test/csv_test.cpp	1
tests/cbor_test/cbor_test.cpp	2
tests/json_test/json_test.cpp	1
tests/networking_tests/repe_plugin_test/repe_plugin_test.cpp	4
include/glaze/rpc/repe/plugin_helper.hpp	4

Fuzzer: yaml_generic

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	34	77.2%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	10	22.7%
All colors	44	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
34	3	LLVMFuzzerTestOneInput	call site: 00003	glz::finalize_top_level_read

Runtime coverage analysis

Covered functions

763

Functions that are reachable but not covered

9

Reachable functions

10

Percentage of reachable functions covered

10.0%

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

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

Function name	source code lines	source lines hit	percentage hit

Files reached

filename	functions hit
fuzzing/yaml_generic.cpp	5
include/glaze/yaml/read.hpp	4
include/glaze/net/http_headers.hpp	1
include/glaze/core/read.hpp	13
include/glaze/core/streaming_state.hpp	2
include/glaze/core/common.hpp	1
include/glaze/util/parse.hpp	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
glz::yaml::parse_block_mapping	/src/glaze/include/glaze/yaml/read.hpp	5	['T', 'Ctx', 'It', 'End', 'int32_t']	5	0	92	23	29	103	0	871	871
glz::process_full_request_with_conn	/src/glaze/include/glaze/net/http_server.hpp	1	['std::shared_ptr ']	17	0	128	19	33	225	12	414	414
glz::read_deduced	/src/glaze/include/glaze/json/read.hpp	4	['auto', 'is_context auto', 'auto', 'auto']	5	0	551	159	199	166	0	413	345
glz::yaml::write_block_sequence	/src/glaze/include/glaze/yaml/write.hpp	5	['T', 'is_context auto', 'B', 'auto', 'int32_t']	10	0	148	36	52	63	5	335	334
glz::detail::cbor_to_json_value	/src/glaze/include/glaze/cbor/cbor_to_json.hpp	6	['auto', 'auto', 'auto', 'Buffer', 'auto', 'uint32_t']	4	0	461	104	124	48	2	294	294
glz::detail::beve_to_json_value	/src/glaze/include/glaze/beve/beve_to_json.hpp	6	['auto', 'auto', 'auto', 'Buffer', 'auto', 'uint32_t']	2	0	554	119	131	20	1	286	286
glz::on_read	/src/glaze/include/glaze/net/websocket_connection.hpp	2	['std::error_code', 'std::size_t']	8	0	20	6	6	202	0	348	228

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

Functions statically reachable by fuzzers

270 / 3577

Cyclomatic complexity statically reachable by fuzzers

2502 / 11765

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.

fuzzing/msgpack_reflection.cpp

Dictionary

Use this with the libFuzzer -dict=DICT.file flag

fuzzing/json_reflection.cpp

Dictionary

Use this with the libFuzzer -dict=DICT.file flag

fuzzing/binary_reflection.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=['LLVMFuzzerTestOneInput']

fuzzing/cbor_reflection.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=['LLVMFuzzerTestOneInput']

fuzzing/cbor_roundtrip_string.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=['LLVMFuzzerTestOneInput']

fuzzing/csv_parsing.cpp

Dictionary

Use this with the libFuzzer -dict=DICT.file flag

fuzzing/json_roundtrip_string.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=['LLVMFuzzerTestOneInput']

fuzzing/msgpack_roundtrip_string.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=['LLVMFuzzerTestOneInput']

fuzzing/json_with_comments.cpp

Dictionary

Use this with the libFuzzer -dict=DICT.file flag

fuzzing/jsonb_reflection.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=['LLVMFuzzerTestOneInput']

fuzzing/cbor_roundtrip_int.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=['LLVMFuzzerTestOneInput']

fuzzing/json_minify.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=['LLVMFuzzerTestOneInput']

fuzzing/json_roundtrip_floating.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=['LLVMFuzzerTestOneInput']

fuzzing/json_roundtrip_int.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=['LLVMFuzzerTestOneInput']

fuzzing/repe_registry.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=['LLVMFuzzerTestOneInput']

fuzzing/json_generic.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=['LLVMFuzzerTestOneInput']

fuzzing/cbor_roundtrip_floating.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=['LLVMFuzzerTestOneInput']

fuzzing/msgpack_roundtrip_floating.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=['LLVMFuzzerTestOneInput']

fuzzing/json_prettify.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=['LLVMFuzzerTestOneInput']

fuzzing/json_jmespath.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=['LLVMFuzzerTestOneInput']

fuzzing/msgpack_roundtrip_int.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=['LLVMFuzzerTestOneInput']

fuzzing/jsonrpc_registry.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=['LLVMFuzzerTestOneInput']

fuzzing/yaml_generic.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=['LLVMFuzzerTestOneInput']

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
_ZN3glz6detail19beve_to_json_numberITnDaXtlNS_4optsELj10ELb1ELb0ELb1ELb1EEERKiRNS_7contextERPKcS9_NSt3__112basic_stringIcNSA_11char_traitsIcEENSA_9allocatorIcEEEEmEEvOT0_OT1_OT2_OT3_RT4_RT5_	90	34	37.77%
_ZN3glz4fromILj2ENSt3__112basic_stringIcNS1_11char_traitsIcEENS1_9allocatorIcEEEEE2opITnDaXtlNS_4optsELj2ELb1ELb0ELb1ELb1ELb0ELb0ELb0ELb0ELj32EEES7_TkNS_10is_contextENS_7contextEPKcSD_EEvRT0_RT1_RT2_T3_	71	20	28.16%
_ZN3glz4atoiITkNSt3__18integralEsKcQsr3stdE11is_signed_vIT_EEEbRS3_RPT0_	32	12	37.5%
_ZN3glz4atoiITkNSt3__18integralExKcQsr3stdE11is_signed_vIT_EEEbRS3_RPT0_	35	12	34.28%
_ZN3glz4atoiITkNSt3__18integralEyKcQsr3stdE13is_unsigned_vIT_EEEbRS3_RPT0_	31	9	29.03%
_ZN3glz12decode_indexITnDaXtlNS_4optsELj10ELb0ELb0ELb1ELb1EEEN9repe_fuzz6nestedELm0ERS3_JETkNS_10is_contextERNS_7contextERPKcS9_Qoo14glaze_object_tIT0_E11reflectableISA_EEEvOT2_OT4_OT5_OT6_DpOT3_	33	9	27.27%
_ZN3glz4fromILj2EfE2opITnDaXtlNS_4optsELj2ELb1ELb0ELb1ELb1ELb0ELb0ELb0ELb0ELj32EEEfTkNS_10is_contextENS_7contextEPKcS6_EEvRT0_RT1_RT2_T3_	66	36	54.54%
_ZN3glz4fromILj30EfE2opITnDaXtlNS_4optsELj30ELb1ELb0ELb1ELb1ELb0ELb0ELb0ELb0ELj32EEERfTkNS_10is_contextERNS_7contextEPKcS8_EEvOT0_hOT1_RT2_RKT3_	32	10	31.25%
_ZN3glz4fromILj30EdE2opITnDaXtlNS_4optsELj30ELb1ELb0ELb1ELb1ELb0ELb0ELb0ELb0ELj32EEERdTkNS_10is_contextERNS_7contextEPKcS8_EEvOT0_hOT1_RT2_RKT3_	32	11	34.37%
_ZN3glz4fromILj30EtE2opITnDaXtlNS_4optsELj30ELb1ELb0ELb1ELb1ELb0ELb0ELb0ELb0ELj32EEERtTkNS_10is_contextERNS_7contextEPKcS8_EEvOT0_hOT1_RT2_RKT3_	31	16	51.61%
_ZN3glz4fromILj30EjE2opITnDaXtlNS_4optsELj30ELb1ELb0ELb1ELb1ELb0ELb0ELb0ELb0ELj32EEERjTkNS_10is_contextERNS_7contextEPKcS8_EEvOT0_hOT1_RT2_RKT3_	31	16	51.61%
_ZN3glz4fromILj30EmE2opITnDaXtlNS_4optsELj30ELb1ELb0ELb1ELb1ELb0ELb0ELb0ELb0ELj32EEERmTkNS_10is_contextERNS_7contextEPKcS8_EEvOT0_hOT1_RT2_RKT3_	31	16	51.61%
_ZN3glz4fromILj30EyE2opITnDaXtlNS_4optsELj30ELb1ELb0ELb1ELb1ELb0ELb0ELb0ELb0ELj32EEERyTkNS_10is_contextERNS_7contextEPKcS8_EEvOT0_hOT1_RT2_RKT3_	31	16	51.61%
_ZN3glz12decode_indexITnDaXtlNS_4optsELj10ELb0ELb0ELb1ELb1EEEN12jsonrpc_fuzz8fuzz_apiELm4ERS3_JETkNS_10is_contextERNS_7contextERPKcS9_Qoo14glaze_object_tIT0_E11reflectableISA_EEEvOT2_OT4_OT5_OT6_DpOT3_	33	9	27.27%
_ZN3glz12decode_indexITnDaXtlNS_4optsELj10ELb0ELb0ELb1ELb1EEEN12jsonrpc_fuzz8fuzz_apiELm11ERS3_JETkNS_10is_contextERNS_7contextERPKcS9_Qoo14glaze_object_tIT0_E11reflectableISA_EEEvOT2_OT4_OT5_OT6_DpOT3_	33	9	27.27%
_ZZN3glz4fromILj450ENSt3__17variantIJDndNS1_12basic_stringIcNS1_11char_traitsIcEENS1_9allocatorIcEEEEbNS1_6vectorINS_12generic_jsonILNS_8num_modeE0ENS_17ordered_small_mapEEENS6_ISD_EEEENSC_ISD_EEEEEE2opITnDaXtlNS_4optsELj450ELb0ELb0ELb1ELb1ELb0ELb0ELb0ELb0ELj1EEERPKcRSH_TkNS_10is_contextERNS_4yaml12yaml_contextESM_EEvOT1_OT2_OT0_T3_ENKUlT_E_clISM_EEDaSZ_	53	11	20.75%
_ZZN3glz4fromILj450ENSt3__17variantIJDndNS1_12basic_stringIcNS1_11char_traitsIcEENS1_9allocatorIcEEEEbNS1_6vectorINS_12generic_jsonILNS_8num_modeE0ENS_17ordered_small_mapEEENS6_ISD_EEEENSC_ISD_EEEEEE2opITnDaXtlNS_4optsELj10ELb1ELb0ELb0ELb1ELb0ELb0ELb0ELb0ELj1EEERPKcRSH_TkNS_10is_contextERNS_4yaml12yaml_contextESM_EEvOT1_OT2_OT0_T3_ENKUlT_E_clISM_EEDaSZ_	53	11	20.75%
_ZZN3glz4fromILj450ENSt3__17variantIJDndNS1_12basic_stringIcNS1_11char_traitsIcEENS1_9allocatorIcEEEEbNS1_6vectorINS_12generic_jsonILNS_8num_modeE0ENS_17ordered_small_mapEEENS6_ISD_EEEENSC_ISD_EEEEEE2opITnDaXtlNS_4yaml9yaml_optsELj450ELb1ELb0ELb1ELh2ELb0ELj1EEERPKcRSH_TkNS_10is_contextERNSK_12yaml_contextESN_EEvOT1_OT2_OT0_T3_ENKUlT_E_clISN_EEDaSZ_	53	11	20.75%
_ZZN3glz4fromILj450ENSt3__17variantIJDndNS1_12basic_stringIcNS1_11char_traitsIcEENS1_9allocatorIcEEEEbNS1_6vectorINS_12generic_jsonILNS_8num_modeE0ENS_17ordered_small_mapEEENS6_ISD_EEEENSC_ISD_EEEEEE2opITnDaXtlNS_4yaml9yaml_optsELj450ELb1ELb0ELb1ELh2ELb0ELj33EEERPKcRSH_TkNS_10is_contextERNSK_12yaml_contextESN_EEvOT1_OT2_OT0_T3_ENKUlT_E_clISN_EEDaSZ_	53	11	20.75%

New fuzzers

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

read.hpp

Target file: /src/glaze/include/glaze/yaml/read.hpp
Target functions: glz::yaml::parse_block_mapping

#include "ada_fuzz_header.h"

int LLVMFuzzerTestOneInput(const uint8_t *data, size_t size) {
  af_safe_gb_init(data, size);

  /* target glz::yaml::parse_block_mapping */
  UNKNOWN_TYPE unknown_0;
  UNKNOWN_TYPE unknown_1;
  UNKNOWN_TYPE unknown_2;
  UNKNOWN_TYPE unknown_3;
  UNKNOWN_TYPE unknown_4;
  glz::yaml::parse_block_mapping(unknown_0, unknown_1, unknown_2, unknown_3, unknown_4);

  af_safe_gb_cleanup();
}

http_server.hpp

Target file: /src/glaze/include/glaze/net/http_server.hpp
Target functions: glz::process_full_request_with_conn

#include "ada_fuzz_header.h"

int LLVMFuzzerTestOneInput(const uint8_t *data, size_t size) {
  af_safe_gb_init(data, size);

  /* target glz::process_full_request_with_conn */
  UNKNOWN_TYPE unknown_5;
  glz::process_full_request_with_conn(unknown_5);

  af_safe_gb_cleanup();
}

read.hpp

Target file: /src/glaze/include/glaze/json/read.hpp
Target functions: glz::read_deduced

#include "ada_fuzz_header.h"

int LLVMFuzzerTestOneInput(const uint8_t *data, size_t size) {
  af_safe_gb_init(data, size);

  /* target glz::read_deduced */
  UNKNOWN_TYPE unknown_6;
  UNKNOWN_TYPE unknown_7;
  UNKNOWN_TYPE unknown_8;
  UNKNOWN_TYPE unknown_9;
  glz::read_deduced(unknown_6, unknown_7, unknown_8, unknown_9);

  af_safe_gb_cleanup();
}

write.hpp

Target file: /src/glaze/include/glaze/yaml/write.hpp
Target functions: glz::yaml::write_block_sequence

#include "ada_fuzz_header.h"

int LLVMFuzzerTestOneInput(const uint8_t *data, size_t size) {
  af_safe_gb_init(data, size);

  /* target glz::yaml::write_block_sequence */
  UNKNOWN_TYPE unknown_10;
  UNKNOWN_TYPE unknown_11;
  UNKNOWN_TYPE unknown_12;
  UNKNOWN_TYPE unknown_13;
  UNKNOWN_TYPE unknown_14;
  glz::yaml::write_block_sequence(unknown_10, unknown_11, unknown_12, unknown_13, unknown_14);

  af_safe_gb_cleanup();
}

cbor_to_json.hpp

Target file: /src/glaze/include/glaze/cbor/cbor_to_json.hpp
Target functions: glz::detail::cbor_to_json_value

#include "ada_fuzz_header.h"

int LLVMFuzzerTestOneInput(const uint8_t *data, size_t size) {
  af_safe_gb_init(data, size);

  /* target glz::detail::cbor_to_json_value */
  UNKNOWN_TYPE unknown_15;
  UNKNOWN_TYPE unknown_16;
  UNKNOWN_TYPE unknown_17;
  UNKNOWN_TYPE unknown_18;
  UNKNOWN_TYPE unknown_19;
  UNKNOWN_TYPE unknown_20;
  glz::detail::cbor_to_json_value(unknown_15, unknown_16, unknown_17, unknown_18, unknown_19, unknown_20);

  af_safe_gb_cleanup();
}

beve_to_json.hpp

Target file: /src/glaze/include/glaze/beve/beve_to_json.hpp
Target functions: glz::detail::beve_to_json_value

#include "ada_fuzz_header.h"

int LLVMFuzzerTestOneInput(const uint8_t *data, size_t size) {
  af_safe_gb_init(data, size);

  /* target glz::detail::beve_to_json_value */
  UNKNOWN_TYPE unknown_21;
  UNKNOWN_TYPE unknown_22;
  UNKNOWN_TYPE unknown_23;
  UNKNOWN_TYPE unknown_24;
  UNKNOWN_TYPE unknown_25;
  UNKNOWN_TYPE unknown_26;
  glz::detail::beve_to_json_value(unknown_21, unknown_22, unknown_23, unknown_24, unknown_25, unknown_26);

  af_safe_gb_cleanup();
}

websocket_connection.hpp

Target file: /src/glaze/include/glaze/net/websocket_connection.hpp
Target functions: glz::on_read

#include "ada_fuzz_header.h"

int LLVMFuzzerTestOneInput(const uint8_t *data, size_t size) {
  af_safe_gb_init(data, size);

  /* target glz::on_read */
  UNKNOWN_TYPE unknown_27;
  UNKNOWN_TYPE unknown_28;
  glz::on_read(unknown_27, unknown_28);

  af_safe_gb_cleanup();
}

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/glaze/tests/json_conformance/json_conformance.cpp	[]	[]
/src/glaze/include/glaze/jsonb/write.hpp	[]	[]
/src/glaze/fuzzing/msgpack_roundtrip_int.cpp	['msgpack_roundtrip_int']	['msgpack_roundtrip_int']
/src/glaze/include/glaze/api/hash.hpp	[]	[]
/src/glaze/include/glaze/jsonb/read.hpp	[]	[]
/src/glaze/include/glaze/api/api.hpp	[]	[]
/src/glaze/tests/simple_float_test/simple_float_test.cpp	[]	[]
/src/glaze/benchmarks/simple_float_benchmark.cpp	[]	[]
/src/glaze/tests/eetf_test/eetf_test.cpp	[]	[]
/src/glaze/include/glaze/json/minify.hpp	['json_minify']	[]
/src/glaze/fuzzing/json_roundtrip_int.cpp	['json_roundtrip_int']	['json_roundtrip_int']
/src/glaze/include/glaze/util/bit_array.hpp	[]	[]
/src/glaze/include/glaze/exceptions/binary_exceptions.hpp	[]	[]
/src/glaze/tests/scratch_directory.hpp	[]	[]
/src/glaze/include/glaze/msgpack/skip.hpp	[]	[]
/src/glaze/tests/beve_test/beve_test.cpp	[]	[]
/src/glaze/include/glaze/util/key_transformers.hpp	[]	[]
/src/glaze/include/glaze/eetf/cmp.hpp	[]	[]
/src/glaze/fuzzing/cbor_roundtrip_int.cpp	['cbor_roundtrip_int']	['cbor_roundtrip_int']
/src/glaze/fuzzing/cbor_roundtrip_string.cpp	['cbor_roundtrip_string']	['cbor_roundtrip_string']
/src/glaze/include/glaze/beve/skip.hpp	[]	[]
/src/glaze/include/glaze/util/memory_pool.hpp	[]	[]
/src/glaze/tests/int_parsing/int_parsing.cpp	[]	[]
/src/glaze/include/glaze/thread/shared_async_vector.hpp	[]	[]
/src/glaze/tests/networking_tests/jsonrpc_registry_test/jsonrpc_registry_test.cpp	[]	[]
/src/glaze/include/glaze/util/atoi.hpp	[]	[]
/src/glaze/include/glaze/core/read.hpp	['yaml_generic']	[]
/src/glaze/tests/cbor_test/cbor_test.cpp	['repe_registry', 'json_jmespath', 'jsonrpc_registry']	[]
/src/glaze/include/glaze/api/std/functional.hpp	[]	[]
/src/glaze/include/glaze/toml/common.hpp	[]	[]
/src/glaze/tests/jsonb_test/jsonb_test.cpp	[]	[]
/src/glaze/tests/networking_tests/cors_test/cors_test.cpp	[]	[]
/src/glaze/include/glaze/core/cast.hpp	[]	[]
/src/glaze/include/glaze/util/progress_bar.hpp	[]	[]
/src/glaze/include/glaze/json/json_stream.hpp	[]	[]
/src/glaze/tests/networking_tests/websocket_autobahn_test/websocket_autobahn_test.cpp	[]	[]
/src/glaze/include/glaze/concepts/container_concepts.hpp	[]	[]
/src/glaze/benchmarks/string_write_benchmark.cpp	[]	[]
/src/glaze/include/glaze/api/xxh64.hpp	[]	[]
/src/glaze/fuzzing/cbor_reflection.cpp	['cbor_reflection']	['cbor_reflection']
/src/glaze/include/glaze/thread/shared_async_map.hpp	[]	[]
/src/glaze/include/glaze/json/float_format.hpp	[]	[]
/src/glaze/benchmarks/float_write_benchmark.cpp	[]	[]
/src/glaze/include/glaze/jsonb/header.hpp	[]	[]
/src/glaze/include/glaze/net/rest_registry_impl.hpp	[]	[]
/src/glaze/include/glaze/core/write_chars.hpp	[]	[]
/src/glaze/include/glaze/format/format_to.hpp	[]	[]
/src/glaze/fuzzing/json_reflection.cpp	['json_reflection']	['json_reflection']
/src/glaze/tests/lib_test/lib_test.cpp	[]	[]
/src/glaze/include/glaze/eetf/read.hpp	[]	[]
/src/glaze/include/glaze/toml/opts.hpp	[]	[]
/src/glaze/include/glaze/rpc/repe/repe_to_jsonrpc.hpp	[]	[]
/src/glaze/tests/csv_test/csv_test.cpp	['repe_registry', 'jsonrpc_registry']	[]
/src/glaze/include/glaze/rpc/repe/repe_registry_impl.hpp	[]	[]
/src/glaze/tests/networking_tests/https_test/https_test.cpp	[]	[]
/src/glaze/tests/networking_tests/http_server_post_test/http_server_post_test.cpp	[]	[]
/src/glaze/tests/networking_tests/http_client_pool_test/http_client_pool_test.cpp	[]	[]
/src/glaze/benchmarks/skip_ws_benchmark.cpp	[]	[]
/src/glaze/tests/networking_tests/http_headers_test/http_headers_test.cpp	[]	[]
/src/glaze/include/glaze/beve/wrappers.hpp	[]	[]
/src/glaze/tests/json_reflection_test/json_reflection_test.cpp	[]	[]
/src/glaze/include/glaze/json/generic_fwd.hpp	[]	[]
/src/glaze/include/glaze/beve/write.hpp	[]	[]
/src/glaze/include/glaze/thread/guard.hpp	[]	[]
/src/glaze/include/glaze/core/buffer_traits.hpp	[]	[]
/src/glaze/tests/chrono_test/chrono_test.cpp	[]	[]
/src/glaze/include/glaze/thread/atomic.hpp	[]	[]
/src/glaze/fuzzing/msgpack_reflection.cpp	['msgpack_reflection']	['msgpack_reflection']
/src/glaze/tests/ordered_map_test/ordered_map_test.cpp	[]	[]
/src/glaze/fuzzing/json_roundtrip_string.cpp	['json_roundtrip_string']	['json_roundtrip_string']
/src/glaze/include/glaze/util/buffer_pool.hpp	[]	[]
/src/glaze/tests/reflection/enum_test.cpp	[]	[]
/src/glaze/include/glaze/util/simple_float.hpp	[]	[]
/src/glaze/include/glaze/exceptions/csv_exceptions.hpp	[]	[]
/src/glaze/include/glaze/api/type_support.hpp	[]	[]
/src/glaze/benchmarks/ordered_map_memory.cpp	[]	[]
/src/glaze/include/glaze/exceptions/json_exceptions.hpp	[]	[]
/src/glaze/include/glaze/yaml/opts.hpp	[]	[]
/src/glaze/include/glaze/file/read_directory.hpp	[]	[]
/src/glaze/tests/networking_tests/http_router_test/http_router_test.cpp	[]	[]
/src/glaze/include/glaze/containers/ordered_map.hpp	[]	[]
/src/glaze/include/glaze/msgpack/common.hpp	[]	[]
/src/glaze/tests/networking_tests/asio_repe/asio_repe.cpp	[]	[]
/src/glaze/include/glaze/toml/write.hpp	[]	[]
/src/glaze/fuzzing/cbor_roundtrip_floating.cpp	['cbor_roundtrip_floating']	['cbor_roundtrip_floating']
/src/glaze/tests/networking_tests/websocket_test/websocket_client_test.cpp	[]	[]
/src/glaze/include/glaze/util/type_traits.hpp	[]	[]
/src/glaze/tests/json_test/non_aggregate_reflection_test.cpp	[]	[]
/src/glaze/include/glaze/rpc/jsonrpc_registry_impl.hpp	[]	[]
/src/glaze/include/glaze/json/study.hpp	[]	[]
/src/glaze/fuzzing/yaml_generic.cpp	['yaml_generic']	['yaml_generic']
/src/glaze/include/glaze/json/raw_string.hpp	[]	[]
/src/glaze/tests/embedded_null_test/embedded_null_test.cpp	[]	[]
/src/glaze/include/glaze/file/file_ops.hpp	[]	[]
/src/glaze/include/glaze/util/env.hpp	[]	[]
/src/glaze/include/glaze/core/std_error_code.hpp	[]	[]
/src/glaze/include/glaze/util/glaze_fast_float.hpp	[]	[]
/src/glaze/include/glaze/util/murmur.hpp	[]	[]
/src/glaze/include/glaze/json/schema.hpp	[]	[]
/src/glaze/include/glaze/core/array_apply.hpp	[]	[]
/src/glaze/include/glaze/jsonb/jsonb_to_json.hpp	['jsonb_reflection']	[]
/src/glaze/fuzzing/msgpack_roundtrip_floating.cpp	['msgpack_roundtrip_floating']	['msgpack_roundtrip_floating']
/src/glaze/include/glaze/bson/write.hpp	[]	[]
/src/glaze/tests/api_test/api_test.cpp	[]	[]
/src/glaze/tests/bson_test/bson_test.cpp	[]	[]
/src/glaze/include/glaze/beve/beve_to_json.hpp	['binary_reflection']	[]
/src/glaze/include/glaze/util/convert.hpp	[]	[]
/src/glaze/include/glaze/rpc/repe/header.hpp	[]	[]
/src/glaze/include/glaze/api/impl.hpp	[]	[]
/src/glaze/include/glaze/cbor/header.hpp	[]	[]
/src/glaze/include/glaze/base64/base64.hpp	[]	[]
/src/glaze/tests/jsonb_sqlite_test/jsonb_sqlite_test.cpp	[]	[]
/src/glaze/tests/cli_menu_test/cli_menu_test.cpp	[]	[]
/src/glaze/tests/json_test/utf8_validation_test.cpp	[]	[]
/src/glaze/tests/jsonrpc_test/jsonrpc_test.cpp	[]	[]
/src/glaze/include/glaze/toml/read.hpp	[]	[]
/src/glaze/include/glaze/ext/jsonrpc.hpp	[]	[]
/src/glaze/include/glaze/net/websocket_client.hpp	[]	[]
/src/glaze/benchmarks/binary_search_benchmark.cpp	[]	[]
/src/glaze/include/glaze/core/istream_buffer.hpp	[]	[]
/src/glaze/include/glaze/core/ptr.hpp	[]	[]
/src/glaze/include/glaze/util/dump.hpp	[]	[]
/src/glaze/include/glaze/record/recorder.hpp	[]	[]
/src/glaze/include/glaze/json/escape_unicode.hpp	[]	[]
/src/glaze/include/glaze/rpc/repe/repe.hpp	[]	[]
/src/glaze/include/glaze/hash/sweethash.hpp	[]	[]
/src/glaze/include/glaze/core/context.hpp	[]	[]
/src/glaze/include/glaze/bson/header.hpp	[]	[]
/src/glaze/include/glaze/json/json_ptr.hpp	[]	[]
/src/glaze/fuzzing/json_with_comments.cpp	['json_with_comments']	['json_with_comments']
/src/glaze/include/glaze/hardware/volatile_array.hpp	[]	[]
/src/glaze/include/glaze/bson/skip.hpp	[]	[]
/src/glaze/include/glaze/containers/inplace_vector.hpp	[]	[]
/src/glaze/tests/exceptions_test/exceptions_test.cpp	[]	[]
/src/glaze/fuzzing/json_generic.cpp	['json_generic']	['json_generic']
/src/glaze/include/glaze/core/write.hpp	['cbor_roundtrip_string', 'json_roundtrip_string', 'msgpack_roundtrip_string', 'cbor_roundtrip_int', 'json_roundtrip_floating', 'json_roundtrip_int', 'cbor_roundtrip_floating', 'msgpack_roundtrip_floating', 'msgpack_roundtrip_int']	[]
/src/glaze/include/glaze/core/common.hpp	['binary_reflection', 'cbor_reflection', 'cbor_roundtrip_string', 'json_roundtrip_string', 'msgpack_roundtrip_string', 'jsonb_reflection', 'cbor_roundtrip_int', 'json_roundtrip_floating', 'json_roundtrip_int', 'cbor_roundtrip_floating', 'msgpack_roundtrip_floating', 'msgpack_roundtrip_int', 'yaml_generic']	[]
/src/glaze/tests/streaming_view_rejection/rejection_cases.cpp	[]	[]
/src/glaze/include/glaze/net/http_router.hpp	[]	[]
/src/glaze/tests/yaml_conformance/yaml_conformance_struct.cpp	[]	[]
/src/glaze/include/glaze/core/manage.hpp	[]	[]
/src/glaze/include/glaze/api/lib.hpp	[]	[]
/src/glaze/include/glaze/net/http_client.hpp	[]	[]
/src/glaze/include/glaze/core/meta.hpp	[]	[]
/src/glaze/include/glaze/eetf/types.hpp	[]	[]
/src/glaze/include/glaze/beve/ptr.hpp	[]	[]
/src/glaze/tests/msgpack_test/msgpack_test.cpp	[]	[]
/src/glaze/tests/networking_tests/http_chunked_test/http_chunked_test.cpp	[]	[]
/src/glaze/include/glaze/json/write.hpp	[]	[]
/src/glaze/include/glaze/cbor/skip.hpp	[]	[]
/src/glaze/include/glaze/core/reflect.hpp	[]	[]
/src/glaze/tests/jmespath/jmespath.cpp	[]	[]
/src/glaze/tests/reflection/reflection.cpp	[]	[]
/src/glaze/examples/json-rpc.cpp	[]	[]
/src/glaze/tests/networking_tests/http_smuggling_test/http_smuggling_test.cpp	[]	[]
/src/glaze/include/glaze/ext/glaze_asio.hpp	[]	[]
/src/glaze/include/glaze/thread/async_string.hpp	[]	[]
/src/glaze/fuzzing/main.cpp	[]	[]
/src/glaze/include/glaze/rpc/repe/plugin_helper.hpp	['repe_registry', 'jsonrpc_registry']	[]
/src/glaze/include/glaze/json/ndjson.hpp	[]	[]
/src/glaze/include/glaze/thread/threadpool.hpp	[]	[]
/src/glaze/tests/eigen_test/eigen_test.cpp	[]	[]
/src/glaze/include/glaze/util/nullable_traits.hpp	[]	[]
/src/glaze/tests/networking_tests/http_client_test/http_client_test.cpp	[]	[]
/src/glaze/include/glaze/json/jmespath.hpp	[]	[]
/src/glaze/include/glaze/json/read.hpp	[]	[]
/src/glaze/tests/ordered_small_map_test/ordered_small_map_test.cpp	[]	[]
/src/glaze/fuzzing/json_minify.cpp	['json_minify']	['json_minify']
/src/glaze/include/glaze/json/chrono_format.hpp	[]	[]
/src/glaze/include/glaze/core/opts.hpp	[]	[]
/src/glaze/include/glaze/exceptions/cbor_exceptions.hpp	[]	[]
/src/glaze/include/glaze/core/ostream_buffer.hpp	[]	[]
/src/glaze/include/glaze/core/convert_struct.hpp	[]	[]
/src/glaze/tests/networking_tests/repe_test/repe_test.cpp	[]	[]
/src/glaze/include/glaze/trace/trace.hpp	[]	[]
/src/glaze/include/glaze/exceptions/msgpack_exceptions.hpp	[]	[]
/src/glaze/fuzzing/jsonrpc_registry.cpp	['repe_registry', 'jsonrpc_registry']	['jsonrpc_registry']
/src/glaze/include/glaze/bson/bson_to_json.hpp	[]	[]
/src/glaze/include/glaze/util/variant.hpp	[]	[]
/src/glaze/include/glaze/msgpack/write.hpp	['cbor_roundtrip_string', 'json_roundtrip_string', 'msgpack_roundtrip_string', 'cbor_roundtrip_int', 'json_roundtrip_floating', 'json_roundtrip_int', 'cbor_roundtrip_floating', 'msgpack_roundtrip_floating', 'msgpack_roundtrip_int']	[]
/src/glaze/include/glaze/yaml/write.hpp	[]	[]
/src/glaze/tests/json_test/json_variant_support_test.cpp	[]	[]
/src/glaze/tests/networking_tests/websocket_test/wss_test.cpp	[]	[]
/src/glaze/tests/json_performance/json_performance.cpp	[]	[]
/src/glaze/include/glaze/stencil/stencilcount.hpp	[]	[]
/src/glaze/tests/networking_tests/http_client_ssl_test/http_client_ssl_test.cpp	[]	[]
/src/glaze/tests/json_test/generic_test.cpp	[]	[]
/src/glaze/include/glaze/json/json_format.hpp	[]	[]
/src/glaze/tests/lib_test/test_lib/test_lib.cpp	[]	[]
/src/glaze/include/glaze/version.hpp	[]	[]
/src/glaze/include/glaze/core/write_wrappers.hpp	[]	[]
/src/glaze/include/glaze/api/trait.hpp	[]	[]
/src/glaze/tests/networking_tests/http_server_test/http_server_request_line_parser_test.cpp	[]	[]
/src/glaze/examples/wrapping_middleware_example.cpp	[]	[]
/src/glaze/tests/float_write_test/float_write_test.cpp	[]	[]
/src/glaze/tests/json_test/allocate_raw_pointers_test.cpp	[]	[]
/src/glaze/tests/json_test/json_test.cpp	['repe_registry', 'jsonrpc_registry']	[]
/src/glaze/fuzzing/json_jmespath.cpp	['json_jmespath']	['json_jmespath']
/src/glaze/examples/repe-jsonrpc-conversion.cpp	[]	[]
/src/glaze/include/glaze/net/url.hpp	[]	[]
/src/glaze/tests/yaml_test/yaml_test.cpp	[]	[]
/src/glaze/include/glaze/json/lazy.hpp	[]	[]
/src/glaze/include/glaze/beve/read.hpp	[]	[]
/src/glaze/include/glaze/json/patch.hpp	[]	[]
/src/glaze/include/glaze/util/uuid.hpp	[]	[]
/src/glaze/include/glaze/util/zmij.hpp	[]	[]
/src/glaze/include/glaze/util/parse.hpp	['yaml_generic']	[]
/src/glaze/benchmarks/ip_address_validation_benchmark.cpp	[]	[]
/src/glaze/include/glaze/util/validate.hpp	[]	[]
/src/glaze/include/glaze/simd/backends.hpp	[]	[]
/src/glaze/tests/toml_test/toml_test.cpp	[]	[]
/src/glaze/tests/networking_tests/http_server_api_tests/http_server_api_tests.cpp	[]	[]
/src/glaze/include/glaze/toml/skip.hpp	[]	[]
/src/glaze/include/glaze/rpc/repe/buffer.hpp	[]	[]
/src/glaze/include/glaze/reflection/get_name.hpp	[]	[]
/src/glaze/include/glaze/util/bit.hpp	[]	[]
/src/glaze/include/glaze/cbor/write.hpp	[]	[]
/src/glaze/tests/json_test/lazy_test.cpp	['repe_registry', 'jsonrpc_registry']	[]
/src/glaze/include/glaze/core/constraint.hpp	[]	[]
/src/glaze/include/glaze/stencil/stencil.hpp	[]	[]
/src/glaze/include/glaze/thread/async_vector.hpp	[]	[]
/src/glaze/include/glaze/msgpack/read.hpp	[]	[]
/src/glaze/include/glaze/eetf/eetf_to_json.hpp	[]	[]
/src/glaze/fuzzing/binary_reflection.cpp	['binary_reflection']	['binary_reflection']
/src/glaze/include/glaze/compare/compare.hpp	[]	[]
/src/glaze/include/glaze/util/for_each.hpp	[]	[]
/src/glaze/benchmarks/lazy_benchmark.cpp	[]	[]
/src/glaze/include/glaze/net/cors.hpp	[]	[]
/src/glaze/include/glaze/util/itoa_40kb.hpp	[]	[]
/src/glaze/include/glaze/exceptions/json_schema_exceptions.hpp	[]	[]
/src/glaze/include/glaze/file/hostname_include.hpp	[]	[]
/src/glaze/include/glaze/bson/read.hpp	[]	[]
/src/glaze/include/glaze/core/seek.hpp	[]	[]
/src/glaze/include/glaze/yaml/read.hpp	['yaml_generic']	[]
/src/glaze/tests/networking_tests/websocket_test/websocket_close_test.cpp	[]	[]
/src/glaze/tests/json_performance/json_perf_common.hpp	[]	[]
/src/glaze/include/glaze/core/wrappers.hpp	[]	[]
/src/glaze/include/glaze/util/compare.hpp	[]	[]
/src/glaze/include/glaze/ext/cli_menu.hpp	[]	[]
/src/glaze/tests/inplace_vector/inplace_vector_test.cpp	[]	[]
/src/glaze/include/glaze/net/http_server.hpp	[]	[]
/src/glaze/include/glaze/json/generic.hpp	['json_generic']	[]
/src/glaze/include/glaze/beve/peek_header.hpp	[]	[]
/src/glaze/include/glaze/csv/write.hpp	[]	[]
/src/glaze/tests/networking_tests/repe_plugin_test/repe_plugin_test.cpp	['repe_registry', 'jsonrpc_registry']	[]
/src/glaze/tests/networking_tests/rest_test/rest_server/rest_server.cpp	[]	[]
/src/glaze/include/glaze/json/ptr.hpp	[]	[]
/src/glaze/include/glaze/util/fast_float.hpp	[]	[]
/src/glaze/include/glaze/beve/size.hpp	[]	[]
/src/glaze/fuzzing/json_roundtrip_floating.cpp	['json_roundtrip_floating']	['json_roundtrip_floating']
/src/glaze/tests/yaml_conformance/yaml_conformance.cpp	[]	[]
/src/glaze/include/glaze/file/file_watch.hpp	[]	[]
/src/glaze/include/glaze/exceptions/jsonb_exceptions.hpp	[]	[]
/src/glaze/include/glaze/eetf/write.hpp	[]	[]
/src/glaze/tests/networking_tests/websocket_test/utf8_test.cpp	[]	[]
/src/glaze/include/glaze/tuplet/tuple.hpp	[]	[]
/src/glaze/include/glaze/simd/neon.hpp	[]	[]
/src/glaze/include/glaze/beve/header.hpp	[]	[]
/src/glaze/include/glaze/json/skip.hpp	[]	[]
/src/glaze/fuzzing/json_exhaustive_roundtrip_int.cpp	[]	[]
/src/glaze/include/glaze/json/invoke.hpp	[]	[]
/src/glaze/include/glaze/reflection/to_tuple.hpp	[]	[]
/src/glaze/tests/networking_tests/http_content_length_test/http_content_length_test.cpp	[]	[]
/src/glaze/include/glaze/util/itoa.hpp	[]	[]
/src/glaze/include/glaze/eetf/ei.hpp	[]	[]
/src/glaze/include/glaze/containers/flat_map.hpp	[]	[]
/src/glaze/include/glaze/util/string_literal.hpp	[]	[]
/src/glaze/include/glaze/thread/async.hpp	[]	[]
/src/glaze/tests/networking_tests/registry_view_test/registry_view_test.cpp	[]	[]
/src/glaze/include/glaze/simd/avx.hpp	[]	[]
/src/glaze/fuzzing/json_prettify.cpp	['json_prettify']	['json_prettify']
/src/glaze/fuzzing/csv_parsing.cpp	['csv_parsing']	['csv_parsing']
/src/glaze/benchmarks/string_write_no_simd.cpp	[]	[]
/src/glaze/include/glaze/simd/utf8_validation.hpp	[]	[]
/src/glaze/include/glaze/beve/lazy.hpp	['json_generic']	[]
/src/glaze/benchmarks/http_benchmark/http_benchmark.cpp	[]	[]
/src/glaze/include/glaze/yaml/skip.hpp	[]	[]
/src/glaze/benchmarks/ordered_map_benchmark.cpp	[]	[]
/src/glaze/include/glaze/eetf/wrappers.hpp	[]	[]
/src/glaze/include/glaze/core/chrono.hpp	[]	[]
/src/glaze/tests/threading_test/threading_test.cpp	[]	[]
/src/glaze/include/glaze/json/max_write_precision.hpp	[]	[]
/src/glaze/include/glaze/yaml/common.hpp	[]	[]
/src/glaze/include/glaze/containers/ordered_small_map.hpp	[]	[]
/src/glaze/tests/yaml_conformance/yaml_conformance_data.cpp	[]	[]
/src/glaze/tests/istream_buffer_test/istream_buffer_test.cpp	[]	[]
/src/glaze/include/glaze/cbor/read.hpp	[]	[]
/src/glaze/include/glaze/net/http_headers.hpp	['yaml_generic']	[]
/src/glaze/include/glaze/json/flatten_map.hpp	[]	[]
/src/glaze/benchmarks/utf8_benchmark.cpp	[]	[]
/src/glaze/include/glaze/json/prettify.hpp	['json_prettify']	[]
/src/glaze/include/glaze/rpc/registry.hpp	[]	[]
/src/glaze/include/glaze/net/http.hpp	[]	[]
/src/glaze/include/glaze/file/write_directory.hpp	[]	[]
/src/glaze/tests/networking_tests/http_response_splitting_test/http_response_splitting_test.cpp	[]	[]
/src/glaze/include/glaze/util/help.hpp	[]	[]
/src/glaze/fuzzing/msgpack_roundtrip_string.cpp	['cbor_roundtrip_string', 'json_roundtrip_string', 'msgpack_roundtrip_string', 'cbor_roundtrip_int', 'json_roundtrip_floating', 'json_roundtrip_int', 'cbor_roundtrip_floating', 'msgpack_roundtrip_floating', 'msgpack_roundtrip_int']	['msgpack_roundtrip_string']
/src/glaze/include/glaze/core/streaming_state.hpp	['binary_reflection', 'cbor_reflection', 'cbor_roundtrip_string', 'json_roundtrip_string', 'msgpack_roundtrip_string', 'jsonb_reflection', 'cbor_roundtrip_int', 'json_roundtrip_floating', 'json_roundtrip_int', 'cbor_roundtrip_floating', 'msgpack_roundtrip_floating', 'msgpack_roundtrip_int', 'yaml_generic']	[]
/src/glaze/include/glaze/jsonb/text_decode.hpp	[]	[]
/src/glaze/include/glaze/cbor/cbor_to_json.hpp	['cbor_reflection']	[]
/src/glaze/include/glaze/json/wrappers.hpp	[]	[]
/src/glaze/tests/json_test/jsonschema_test.cpp	[]	[]
/src/glaze/include/glaze/csv/read.hpp	[]	[]
/src/glaze/include/glaze/net/websocket_connection.hpp	[]	[]
/src/glaze/include/glaze/simd/sse.hpp	[]	[]
/src/glaze/tests/roundtrip/roundtrip.cpp	[]	[]
/src/glaze/include/glaze/core/format_str.hpp	[]	[]
/src/glaze/include/glaze/exceptions/core_exceptions.hpp	[]	[]
/src/glaze/tests/networking_tests/http_examples/http_examples.cpp	[]	[]
/src/glaze/fuzzing/repe_registry.cpp	['repe_registry']	['repe_registry']
/src/glaze/fuzzing/jsonb_reflection.cpp	['jsonb_reflection']	['jsonb_reflection']

Directories in report

Directory
/src/glaze/tests/networking_tests/http_smuggling_test/
/src/glaze/tests/jsonb_test/
/src/glaze/tests/reflection/
/src/glaze/tests/ordered_small_map_test/
/src/glaze/include/glaze/containers/
/src/glaze/include/glaze/util/
/src/glaze/include/glaze/trace/
/src/glaze/include/glaze/
/src/glaze/tests/threading_test/
/src/glaze/include/glaze/simd/
/src/glaze/tests/networking_tests/jsonrpc_registry_test/
/src/glaze/include/glaze/rpc/repe/
/src/glaze/tests/networking_tests/asio_repe/
/src/glaze/include/glaze/reflection/
/src/glaze/include/glaze/file/
/src/glaze/include/glaze/eetf/
/src/glaze/include/glaze/stencil/
/src/glaze/tests/eigen_test/
/src/glaze/tests/embedded_null_test/
/src/glaze/include/glaze/concepts/
/src/glaze/tests/bson_test/
/src/glaze/include/glaze/tuplet/
/src/glaze/tests/float_write_test/
/src/glaze/tests/networking_tests/http_client_pool_test/
/src/glaze/tests/networking_tests/registry_view_test/
/src/glaze/tests/msgpack_test/
/src/glaze/tests/jmespath/
/src/glaze/tests/int_parsing/
/src/glaze/tests/inplace_vector/
/src/glaze/tests/networking_tests/websocket_test/
/src/glaze/include/glaze/api/std/
/src/glaze/tests/yaml_test/
/src/glaze/tests/beve_test/
/src/glaze/tests/networking_tests/http_router_test/
/src/glaze/include/glaze/base64/
/src/glaze/tests/networking_tests/http_client_test/
/src/glaze/include/glaze/api/
/src/glaze/tests/eetf_test/
/src/glaze/include/glaze/core/
/src/glaze/tests/jsonrpc_test/
/src/glaze/tests/json_test/
/src/glaze/tests/yaml_conformance/
/src/glaze/tests/json_performance/
/src/glaze/include/glaze/yaml/
/src/glaze/tests/streaming_view_rejection/
/src/glaze/tests/simple_float_test/
/src/glaze/include/glaze/toml/
/src/glaze/benchmarks/http_benchmark/
/src/glaze/include/glaze/hash/
/src/glaze/tests/cli_menu_test/
/src/glaze/include/glaze/compare/
/src/glaze/include/glaze/csv/
/src/glaze/tests/networking_tests/http_content_length_test/
/src/glaze/tests/networking_tests/cors_test/
/src/glaze/benchmarks/
/src/glaze/include/glaze/record/
/src/glaze/tests/networking_tests/http_headers_test/
/src/glaze/include/glaze/rpc/
/src/glaze/tests/networking_tests/http_client_ssl_test/
/src/glaze/tests/networking_tests/https_test/
/src/glaze/tests/networking_tests/http_chunked_test/
/src/glaze/include/glaze/net/
/src/glaze/tests/networking_tests/http_response_splitting_test/
/src/glaze/tests/cbor_test/
/src/glaze/tests/roundtrip/
/src/glaze/tests/networking_tests/http_examples/
/src/glaze/tests/chrono_test/
/src/glaze/tests/networking_tests/repe_plugin_test/
/src/glaze/include/glaze/ext/
/src/glaze/include/glaze/beve/
/src/glaze/include/glaze/msgpack/
/src/glaze/tests/lib_test/
/src/glaze/tests/networking_tests/http_server_post_test/
/src/glaze/tests/networking_tests/http_server_test/
/src/glaze/tests/networking_tests/repe_test/
/src/glaze/include/glaze/bson/
/src/glaze/tests/toml_test/
/src/glaze/tests/api_test/
/src/glaze/include/glaze/json/
/src/glaze/tests/csv_test/
/src/glaze/fuzzing/
/src/glaze/tests/json_conformance/
/src/glaze/examples/
/src/glaze/tests/ordered_map_test/
/src/glaze/tests/networking_tests/rest_test/rest_server/
/src/glaze/include/glaze/thread/
/src/glaze/tests/json_reflection_test/
/src/glaze/tests/
/src/glaze/tests/jsonb_sqlite_test/
/src/glaze/include/glaze/jsonb/
/src/glaze/tests/networking_tests/websocket_autobahn_test/
/src/glaze/tests/exceptions_test/
/src/glaze/include/glaze/hardware/
/src/glaze/tests/lib_test/test_lib/
/src/glaze/tests/networking_tests/http_server_api_tests/
/src/glaze/tests/istream_buffer_test/
/src/glaze/include/glaze/format/
/src/glaze/include/glaze/cbor/
/src/glaze/include/glaze/exceptions/

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

Function in each files in report

Target sink	Callsite location	Reached by fuzzer	Covered by Fuzzers

This section contains multiple tables, each table contains a list of sink functions/methods found in the project for one of the CWE supported by the sink analyser, together with information like which fuzzers statically reach the sink functions/methods and possible call path to that sink functions/methods if it is not statically reached by any fuzzers. Column 1 is the function/method name of the sink functions/methods found in the project. Column 2 lists all fuzzers (or no fuzzers at all) that have covered that particular function method statically. Column 3 shows a list of possible call paths to reach the specific function/method call if none of the fuzzers cover the target function/method calls. Lastly, column 4 shows possible fuzzer blockers that prevent an existing fuzzer from reaching the target sink functions/methods dynamically.

Sink functions/methods found for CWE416

Target sink	Reached by fuzzer	Function call path	Possible branch blockers
get	[]	Path 1 Path 2	N/A

Sink functions/methods found for CWE20

Target sink	Reached by fuzzer	Function call path	Possible branch blockers
get	[]	Path 1 Path 2	N/A

Sink functions/methods found for CWE22

Target sink	Reached by fuzzer	Function call path	Possible branch blockers
write	[]	Path 1 Path 2	N/A