Fuzz introspector
For issues and ideas: https://github.com/ossf/fuzz-introspector/issues
Project coverage
Per-fuzzer coverage

Table of contents

Project overview: wasm3
High level conclusions
Reachability and coverage overview
Fuzzers overview
Project functions overview
Fuzzer details
Fuzzer: fuzzer
Call tree
Fuzz blockers
Runtime coverage analysis
Files reached
Analyses and suggestions
Optimal target analysis
Remaining optimal interesting functions
All functions overview
Fuzz engine guidance
/src/wasm3/platforms/app_fuzz/fuzzer.c
Dictionary
Fuzzer function priority
Runtime coverage analysis
Complex functions with low coverage
Files and Directories in report
Files in report
Directories in report
Metadata section
Report generation date: 2026-09-13

Project overview: wasm3

High level conclusions

Reachability and coverage overview

Functions statically reachable by fuzzers
18.0%
200 / 1085
Cyclomatic complexity statically reachable by fuzzers
28.0%
1277 / 4549
Runtime code coverage of functions
34.0%
367 / 1085

Warning: The number of runtime covered functions are larger than the number of reachable functions. This means that Fuzz Introspector found there are more functions covered at runtime than what is considered reachable based on the static analysis. This is a limitation in the analysis as anything covered at runtime is by definition reachable by the fuzzers.
This is likely due to a limitation in the static analysis. In this case, the count of functions covered at runtime is the true value, which means this is what should be considered "achieved" by the fuzzer.

Use the project functions table below to query all functions that were not covered at runtime.

Fuzzers overview

Fuzzer Fuzzer filename Functions Reached Functions unreached Fuzzer depth Files reached Basic blocks reached Cyclomatic complexity Details
fuzzer /src/wasm3/platforms/app_fuzz/fuzzer.c 212 905 12 16 3141 1311 fuzzer.c

Project functions overview

The following table shows data about each function in the project. The functions included in this table correspond to all functions that exist in the executables of the fuzzers. As such, there may be functions that are from third-party libraries.

For further technical details on the meaning of columns in the below table, please see the Glossary .

Func name Functions filename Args Function call depth Reached by Fuzzers Runtime reached by Fuzzers Combined reached by Fuzzers Fuzzers runtime hit Func lines hit % I Count BB Count Cyclomatic complexity Functions reached Reached by functions Accumulated cyclomatic complexity Undiscovered complexity

Fuzzer details

Fuzzer: fuzzer

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

Full calltree

Call tree overview bitmap:

The distribution of callsites in terms of coloring is
Color Runtime hitcount Callsite count Percentage
red 0 108 18.0%
gold [1:9] 52 8.71%
yellow [10:29] 36 6.03%
greenyellow [30:49] 27 4.52%
lawngreen 50+ 374 62.6%
All colors 597 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
14 517 v_validate_body call site: 00517 v_pop_expect
11 69 LinkImports call site: 00069 Module_HasExport
9 81 LinkImports call site: 00081 Module_HasExport
9 487 v_validate_body call site: 00487 v_cvtop
8 91 LinkImports call site: 00091 Module_HasExport
6 270 PrepareFoundFunction call site: 00270 CompileFunction
4 429 v_validate_body call site: 00429 v_pop_expect
4 498 v_validate_body call site: 00498 v_pop_expect
3 100 LinkImports call site: 00100 Module_HasExport
3 246 ResolveElements call site: 00246 ReadLEB_i7
3 250 ReadLEB_i7 call site: 00250 ReadLEB_u32
3 390 v_validate_body call site: 00390 ReadLEB_u32

Runtime coverage analysis

Covered functions
371
Functions that are reachable but not covered
23
Reachable functions
212
Percentage of reachable functions covered
89.15%
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
/src/wasm3/platforms/app_fuzz/fuzzer.c 1
m3_env.c 51
m3_core.c 27
m3_function.c 11
m3_code.c 7
m3_parse.c 3
m3_module.c 3
m3_host_posix.h 7
m3_function.h 1
m3_env.h 3
m3_compile.c 52
m3_exec.h 3
m3_compile.h 4
m3_exec_defs.h 1
m3_validate.c 26
m3_info.c 1

Analyses and suggestions

Optimal target analysis

Remaining optimal interesting functions

The following table shows a list of functions that are optimal targets. Optimal targets are identified by finding the functions that in combination, yield a high code coverage.

Func name Functions filename Arg count Args Function depth hitcount instr count bb count cyclomatic complexity Reachable functions Incoming references total cyclomatic complexity Unreached complexity
Compile_If /src/wasm3/source/m3_compile.c 2 ['N/A', 'short'] 12 0 162 38 17 120 0 578 276
ParseSection_Import /src/wasm3/source/m3_parse.c 3 ['N/A', 'N/A', 'N/A'] 5 0 344 81 33 33 0 204 153
Compile_SetLocal /src/wasm3/source/m3_compile.c 2 ['N/A', 'short'] 8 0 208 48 22 57 0 249 81
Compile_Call /src/wasm3/source/m3_compile.c 2 ['N/A', 'short'] 9 0 232 50 21 72 0 272 66
Compile_Ref_Func /src/wasm3/source/m3_compile.c 2 ['N/A', 'short'] 8 0 72 15 7 44 0 168 53
m3_CallArgv /src/wasm3/source/m3_env.c 3 ['N/A', 'int', 'N/A'] 5 0 217 42 13 27 0 101 51
Compile_Branch /src/wasm3/source/m3_compile.c 2 ['N/A', 'short'] 10 0 402 98 45 78 0 313 47
Compile_Select_Typed /src/wasm3/source/m3_compile.c 2 ['N/A', 'short'] 8 0 57 12 6 57 0 216 45
Compile_Table_GrowFill /src/wasm3/source/m3_compile.c 2 ['N/A', 'short'] 8 0 64 14 7 58 0 205 44
ParseSection_Element /src/wasm3/source/m3_parse.c 3 ['N/A', 'N/A', 'N/A'] 10 0 379 83 35 77 0 336 41

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

Functions statically reachable by fuzzers
28.0%
299 / 1085
Cyclomatic complexity statically reachable by fuzzers
47.0%
2120 / 4549

All functions overview

If you implement fuzzers for these functions, the status of all functions in the project will be:

Func name Functions filename Args Function call depth Reached by Fuzzers Runtime reached by Fuzzers Combined reached by Fuzzers Fuzzers runtime hit Func lines hit % I Count BB Count Cyclomatic complexity Functions reached Reached by functions Accumulated cyclomatic complexity Undiscovered complexity

Fuzz engine guidance

This sections provides heuristics that can be used as input to a fuzz engine when running a given fuzz target. The current focus is on providing input that is usable by libFuzzer.

/src/wasm3/platforms/app_fuzz/fuzzer.c

Dictionary

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


Fuzzer function priority

Use one of these functions as input to libfuzzer with flag: -focus_function name 

-focus_function=['v_validate_body', 'LinkImports', 'PrepareFoundFunction', 'ResolveElements']

Runtime coverage analysis

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
GetFoldOp 52 14 26.92% ['fuzzer']
CopyStackSlotsR 39 18 46.15% ['fuzzer']
m3_CallVL 45 15 33.33% ['fuzzer']
ResolveElements 46 24 52.17% ['fuzzer']
LinkImports 89 40 44.94% ['fuzzer']

Files and Directories in report

This section shows which files and directories are considered in this report. The main reason for showing this is fuzz introspector may include more code in the reasoning than is desired. This section helps identify if too many files/directories are included, e.g. third party code, which may be irrelevant for the threat model. In the event too much is included, fuzz introspector supports a configuration file that can exclude data from the report. See the following link for more information on how to create a config file: link

Files in report

Source file Reached by Covered by
[] []
/src/wasm3/source/m3_validate.c ['fuzzer'] ['fuzzer']
/src/wasm3/source/m3_core.c ['fuzzer'] ['fuzzer']
/src/wasm3/source/m3_compile.c ['fuzzer'] ['fuzzer']
/src/wasm3/source/m3_exec.h ['fuzzer'] ['fuzzer']
/src/wasm3/source/m3_exec_defs.h ['fuzzer'] ['fuzzer']
/src/wasm3/source/m3_compile.h ['fuzzer'] ['fuzzer']
/src/wasm3/source/m3_function.h ['fuzzer'] ['fuzzer']
/src/wasm3/source/m3_module.c ['fuzzer'] ['fuzzer']
/src/wasm3/source/m3_env.h ['fuzzer'] ['fuzzer']
/src/wasm3/source/m3_function.c ['fuzzer'] ['fuzzer']
/src/wasm3/platforms/app_fuzz/fuzzer.c ['fuzzer'] ['fuzzer']
/src/wasm3/source/m3_host.h [] []
/src/wasm3/source/m3_core.h [] []
/src/wasm3/source/m3_env.c ['fuzzer'] ['fuzzer']
/src/wasm3/source/m3_host_posix.h ['fuzzer'] ['fuzzer']
/src/wasm3/source/m3_code.c ['fuzzer'] ['fuzzer']
/src/wasm3/source/m3_math_utils.h [] []
/src/wasm3/source/m3_parse.c ['fuzzer'] ['fuzzer']
/src/wasm3/source/m3_info.c ['fuzzer'] ['fuzzer']

Directories in report

Directory
/src/wasm3/platforms/app_fuzz/
/src/wasm3/source/

Metadata section

This sections shows the raw data that is used to produce this report. This is mainly used for further processing and developer debugging.

Fuzzer Calltree file Program data file Coverage file
fuzzer fuzzerLogFile-0-kLGqhxI4LV.data fuzzerLogFile-0-kLGqhxI4LV.data.yaml fuzzer.covreport