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: 2025-07-11

Project overview: wasm3

High level conclusions

Reachability and coverage overview

Functions statically reachable by fuzzers
17.0%
129 / 761
Cyclomatic complexity statically reachable by fuzzers
22.0%
559 / 2527
Runtime code coverage of functions
26.0%
199 / 761

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 135 637 12 12 1194 577 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 9 3.30%
gold [1:9] 11 4.04%
yellow [10:29] 35 12.8%
greenyellow [30:49] 12 4.41%
lawngreen 50+ 205 75.3%
All colors 272 100

Fuzz blockers

The followings are the branches where fuzzer fails to bypass.

Unique non-covered Complexity Unique Reachable Complexities Unique Reachable Functions All non-covered Complexity All Reachable Complexity Function Name Function Callsite Blocked Branch
0 0 None 0 677 Compile_BranchTable call site: 00000 /src/wasm3/source/m3_compile.c:1573
0 0 None 0 574 CompileBlock call site: 00067 /src/wasm3/source/m3_compile.c:2697
0 0 None 0 47 Compile_End call site: 00000 /src/wasm3/source/m3_compile.c:1280
0 0 None 0 30 EvaluateExpression call site: 00056 /src/wasm3/source/m3_env.c:288
0 0 None 0 10 PushConst call site: 00000 /src/wasm3/source/m3_compile.c:747
0 0 None 0 2 m3_NewRuntime call site: 00019 /src/wasm3/source/m3_env.c:186
0 0 None 0 2 ParseSection_Custom call site: 00000 /src/wasm3/source/m3_parse.c:560
0 0 None 0 0 CompileBlockStatements call site: 00111 /src/wasm3/source/m3_compile.c:2615
0 0 None 0 0 EnsureCodePageNumLines call site: 00126 /src/wasm3/source/m3_compile.c:36
0 0 None 0 0 ResizeMemory call site: 00051 /src/wasm3/source/m3_env.c:371
0 0 None 0 0 GetFunctionNames call site: 00000 /src/wasm3/source/m3_function.c:159

Runtime coverage analysis

Covered functions
200
Functions that are reachable but not covered
8
Reachable functions
135
Percentage of reachable functions covered
94.07%
NB: The sum of covered functions and functions that are reachable but not covered need not be equal to Reachable functions . This is because the reachability analysis is an approximation and thus at runtime some functions may be covered that are not included in the reachability analysis. This is a limitation of our static analysis capabilities.
Warning: The number of covered functions are larger than the number of reachable functions. This means that there are more functions covered at runtime than are extracted using static analysis. This is likely a result of the static analysis component failing to extract the right call graph or the coverage runtime being compiled with sanitizers in code that the static analysis has not analysed. This can happen if lto/gold is not used in all places that coverage instrumentation is used.
Function name source code lines source lines hit percentage hit

Files reached

filename functions hit
/src/wasm3/platforms/app_fuzz/fuzzer.c 1
m3_env.c 27
m3_core.c 16
m3_function.c 11
m3_code.c 7
m3_parse.c 2
m3_module.c 2
m3_compile.c 56
m3_compile.h 4
m3_exec.h 2
m3_exec_defs.h 1
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_Branch /src/wasm3/source/m3_compile.c 2 ['N/A', 'short'] 10 0 328 66 31 69 0 261 65
Compile_If /src/wasm3/source/m3_compile.c 2 ['N/A', 'short'] 12 0 132 26 12 91 0 370 56
ParseSection_Import /src/wasm3/source/m3_parse.c 3 ['N/A', 'N/A', 'N/A'] 4 0 272 44 16 19 0 83 48
Compile_Const_i32 /src/wasm3/source/m3_compile.c 2 ['N/A', 'short'] 8 0 40 6 3 39 0 147 45
Compile_CallIndirect /src/wasm3/source/m3_compile.c 2 ['N/A', 'short'] 9 0 130 21 9 87 0 330 35

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

Functions statically reachable by fuzzers
22.0%
169 / 761
Cyclomatic complexity statically reachable by fuzzers
32.0%
808 / 2527

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=['InitElements', 'CompileFunction', 'Environment_AddFuncType', 'm3_NewRuntime', 'Function_Release', 'Pop']

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
PushConst 84 41 48.80% ['fuzzer']
InitElements 36 14 38.88% ['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_core.c ['fuzzer'] ['fuzzer']
[] []
/src/wasm3/source/m3_math_utils.h [] []
/src/wasm3/source/m3_code.c ['fuzzer'] ['fuzzer']
/src/wasm3/source/m3_compile.c ['fuzzer'] ['fuzzer']
/src/wasm3/source/m3_compile.h ['fuzzer'] ['fuzzer']
/src/wasm3/source/m3_exec_defs.h ['fuzzer'] ['fuzzer']
/src/wasm3/source/m3_exec.h ['fuzzer'] ['fuzzer']
/src/wasm3/source/m3_parse.c ['fuzzer'] ['fuzzer']
/src/wasm3/source/m3_info.c ['fuzzer'] ['fuzzer']
/src/wasm3/source/m3_env.c ['fuzzer'] ['fuzzer']
/src/wasm3/source/m3_module.c ['fuzzer'] ['fuzzer']
/src/wasm3/platforms/app_fuzz/fuzzer.c ['fuzzer'] ['fuzzer']
/src/wasm3/source/m3_function.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-brYyDi4Jur.data fuzzerLogFile-0-brYyDi4Jur.data.yaml fuzzer.covreport