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-08-31

Project overview: wasm3

High level conclusions

Reachability and coverage overview

Functions statically reachable by fuzzers
16.0%
166 / 1051
Cyclomatic complexity statically reachable by fuzzers
25.0%
1101 / 4346
Runtime code coverage of functions
28.9%
310 / 1051

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 172 893 12 15 2703 1119 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 174 32.2%
gold [1:9] 6 1.11%
yellow [10:29] 10 1.85%
greenyellow [30:49] 9 1.66%
lawngreen 50+ 341 63.1%
All colors 540 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
25 125 m3Error call site: 00125 Compile_Operator
23 178 GetPC call site: 00178 EmitSlotNumOfStackTopAndPop
22 509 GetFunctionArgType call site: 00509 CompileBlockStatements
15 162 ReleaseCodePageNoTrack call site: 00162 PreserveRegisterIfOccupied
11 65 LinkImports call site: 00065 Module_HasExport
9 77 LinkImports call site: 00077 Module_HasExport
8 87 LinkImports call site: 00087 Module_HasExport
8 500 v_validate_body call site: 00500 AcquireCompilationCodePage
7 117 EvaluateExpression call site: 00117 CompileBlockStatements
6 153 EnsureCodePageNumLines call site: 00153 AcquireCodePageWithCapacity
4 241 PrepareFoundFunction call site: 00241 CompileFunction
4 460 v_validate_body call site: 00460 v_pop_expect

Runtime coverage analysis

Covered functions
312
Functions that are reachable but not covered
14
Reachable functions
172
Percentage of reachable functions covered
91.86%
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 37
m3_core.c 21
m3_function.c 11
m3_code.c 7
m3_parse.c 3
m3_module.c 3
m3_function.h 1
m3_env.h 3
m3_compile.c 46
m3_compile.h 4
m3_exec.h 2
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 161 38 17 112 0 530 277
ParseSection_Import /src/wasm3/source/m3_parse.c 3 ['N/A', 'N/A', 'N/A'] 5 0 344 81 33 33 0 204 146
Compile_SetLocal /src/wasm3/source/m3_compile.c 2 ['N/A', 'short'] 8 0 208 48 22 57 0 248 81
m3_CallArgv /src/wasm3/source/m3_env.c 3 ['N/A', 'int', 'N/A'] 3 0 205 40 12 16 0 72 66
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
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
Compile_Branch /src/wasm3/source/m3_compile.c 2 ['N/A', 'short'] 10 0 372 90 42 78 0 310 44
ParseSection_Element /src/wasm3/source/m3_parse.c 3 ['N/A', 'N/A', 'N/A'] 11 0 379 83 35 70 0 295 41

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

Functions statically reachable by fuzzers
26.0%
270 / 1051
Cyclomatic complexity statically reachable by fuzzers
45.0%
1952 / 4346

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=['m3Error', 'GetPC', 'GetFunctionArgType', 'ReleaseCodePageNoTrack', 'LinkImports', 'v_validate_body', 'EvaluateExpression', 'EnsureCodePageNumLines']

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
ResolveElements 53 26 49.05% ['fuzzer']
LinkImports 89 36 40.44% ['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_validate.c ['fuzzer'] ['fuzzer']
/src/wasm3/source/m3_code.c ['fuzzer'] ['fuzzer']
/src/wasm3/platforms/app_fuzz/fuzzer.c ['fuzzer'] ['fuzzer']
/src/wasm3/source/m3_info.c ['fuzzer'] ['fuzzer']
/src/wasm3/source/m3_compile.c ['fuzzer'] ['fuzzer']
/src/wasm3/source/m3_core.h [] []
/src/wasm3/source/m3_exec_defs.h ['fuzzer'] ['fuzzer']
/src/wasm3/source/m3_function.c ['fuzzer'] ['fuzzer']
/src/wasm3/source/m3_exec.h ['fuzzer'] ['fuzzer']
/src/wasm3/source/m3_compile.h ['fuzzer'] ['fuzzer']
/src/wasm3/source/m3_env.h ['fuzzer'] ['fuzzer']
/src/wasm3/source/m3_parse.c ['fuzzer'] ['fuzzer']
/src/wasm3/source/m3_function.h ['fuzzer'] ['fuzzer']
/src/wasm3/source/m3_module.c ['fuzzer'] ['fuzzer']
/src/wasm3/source/m3_math_utils.h [] []
/src/wasm3/source/m3_env.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-MWIeHaJQFu.data fuzzerLogFile-0-MWIeHaJQFu.data.yaml fuzzer.covreport