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

Table of contents

Project overview: sqlite3
High level conclusions
Reachability and coverage overview
Fuzzers overview
Project functions overview
Fuzzer details
Fuzzer: ossfuzz
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
test/ossfuzz.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-07-24

Project overview: sqlite3

High level conclusions

Reachability and coverage overview

Functions statically reachable by fuzzers
69.0%
1926 / 2773
Cyclomatic complexity statically reachable by fuzzers
76.0%
19695 / 25859
Runtime code coverage of functions
79.0%
2194 / 2773

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
ossfuzz test/ossfuzz.c 1942 919 85 2 66681 19734 ossfuzz.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: ossfuzz

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 11764 73.2%
gold [1:9] 108 0.67%
yellow [10:29] 35 0.21%
greenyellow [30:49] 10 0.06%
lawngreen 50+ 4147 25.8%
All colors 16064 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
1368 12804 sqlite3DbSpanDup call site: 12804 sqlite3AddPrimaryKey
680 15257 sqlite3_hard_heap_limit64 call site: 15257 sqlite3Pragma
628 6222 sqlite3_value_int call site: 06222 sqlite3ExprCode
521 5548 sqlite3VdbeChangeToNoop call site: 05548 sqlite3ConstructBloomFilter
472 6853 sqlite3VdbeJumpHereOrPopInst call site: 06853 sqlite3WhereEnd
405 5140 sqlite3LogEstFromDouble call site: 05140 constructAutomaticIndex
352 4410 sqlite3_str_new call site: 04410 exprAnalyze
305 14175 sqlite3VdbeTakeOpArray call site: 14175 sqlite3CodeDropTable
291 4117 sqlite3VdbeChangeOpcode call site: 04117 sqlite3WhereBegin
282 12291 sqlite3Step call site: 12291 sqlite3InitOne
259 4880 sqlite3VdbeChangeP3 call site: 04880 exprAnalyze
219 3279 sqlite3Dequote call site: 03279 flattenSubquery

Runtime coverage analysis

Covered functions
2196
Functions that are reachable but not covered
207
Reachable functions
1942
Percentage of reachable functions covered
89.34%
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
test/ossfuzz.c 5
bld/sqlite3.c 1922

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
jsonExtractFunc /src/sqlite3/bld/sqlite3.c 3 ['N/A', 'int', 'N/A'] 43 0 378 70 24 261 0 2173 839
resolveExprStep /src/sqlite3/bld/sqlite3.c 2 ['N/A', 'N/A'] 46 0 2719 473 129 317 1 2690 510
strftimeFunc /src/sqlite3/bld/sqlite3.c 3 ['N/A', 'int', 'N/A'] 39 0 599 93 17 200 0 1515 259
selectExpander /src/sqlite3/bld/sqlite3.c 2 ['N/A', 'N/A'] 70 0 2420 404 116 1922 0 19705 236
unixOpen /src/sqlite3/bld/sqlite3.c 5 ['N/A', 'N/A', 'N/A', 'int', 'N/A'] 39 0 1145 242 67 188 0 1403 179
renameColumnFunc /src/sqlite3/bld/sqlite3.c 3 ['N/A', 'int', 'N/A'] 70 0 779 118 39 1931 0 19617 162
sqlite3_test_control /src/sqlite3/bld/sqlite3.c 1 ['int'] 45 0 1626 225 59 278 0 1933 153

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

Functions statically reachable by fuzzers
76.0%
2118 / 2773
Cyclomatic complexity statically reachable by fuzzers
85.0%
21892 / 25859

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.

test/ossfuzz.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=['sqlite3DbSpanDup', 'sqlite3_hard_heap_limit64', 'sqlite3_value_int', 'sqlite3VdbeChangeToNoop', 'sqlite3VdbeJumpHereOrPopInst', 'sqlite3LogEstFromDouble', 'sqlite3_str_new', 'sqlite3VdbeTakeOpArray', 'sqlite3VdbeChangeOpcode', 'sqlite3Step']

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
sqlite3_vtab_config 39 21 53.84% ['ossfuzz']
sqlite3_config 160 16 10.0% ['ossfuzz']
unixWrite 37 14 37.83% ['ossfuzz']
unixFileControl 144 32 22.22% ['ossfuzz']
fcntlSizeHint 38 14 36.84% ['ossfuzz']
sqlite3PagerSharedLock 106 17 16.03% ['ossfuzz']
pager_incr_changecounter 41 13 31.70% ['ossfuzz']
writeSuperJournal 41 13 31.70% ['ossfuzz']
syncJournal 64 15 23.43% ['ossfuzz']
sqlite3WalClose 39 5 12.82% ['ossfuzz']
vdbeCommit 166 55 33.13% ['ossfuzz']
sqlite3VtabSavepoint 36 7 19.44% ['ossfuzz']
hasSharedCacheTableLock 39 8 20.51% ['ossfuzz']
sqlite3BtreeOpen 220 105 47.72% ['ossfuzz']
sqlite3PagerSetFlags 36 19 52.77% ['ossfuzz']
sqlite3VtabBegin 32 7 21.87% ['ossfuzz']
exprCodeInlineFunction 78 38 48.71% ['ossfuzz']
sqlite3VtabOverloadFunction 45 19 42.22% ['ossfuzz']
existsToJoin 45 21 46.66% ['ossfuzz']
countOfViewOptimization 68 25 36.76% ['ossfuzz']
sqlite3WindowCodeInit 61 32 52.45% ['ossfuzz']
sqlite3ParseUri 167 30 17.96% ['ossfuzz']
sqlite3AutoLoadExtensions 33 9 27.27% ['ossfuzz']
createCollation 44 20 45.45% ['ossfuzz']

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/sqlite3/test/ossfuzz.c ['ossfuzz'] ['ossfuzz']
/src/sqlite3/bld/sqlite3.c ['ossfuzz'] ['ossfuzz']

Directories in report

Directory
/src/sqlite3/test/
/src/sqlite3/bld/

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
ossfuzz fuzzerLogFile-0-WuqilgqIGh.data fuzzerLogFile-0-WuqilgqIGh.data.yaml ossfuzz.covreport