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

Table of contents

Project overview: ipykernel
High level conclusions
Reachability and coverage overview
Fuzzers overview
Project functions overview
Fuzzer details
Fuzzer: fuzz_serialization_roundtrip
Call tree
Fuzz blockers
Runtime coverage analysis
Files reached
Fuzzer: fuzz_unpack_roundtrip
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/fuzz_serialization_roundtrip.py
Dictionary
Fuzzer function priority
/src/fuzz_unpack_roundtrip.py
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-01

Project overview: ipykernel

High level conclusions

Reachability and coverage overview

Functions statically reachable by fuzzers
0.0%
2 / 496
Cyclomatic complexity statically reachable by fuzzers
0.0%
6 / 1642
Runtime code coverage of functions
0.0%
1 / 496

Fuzzers overview

Fuzzer Fuzzer filename Functions Reached Functions unreached Fuzzer depth Files reached Basic blocks reached Cyclomatic complexity Details
fuzz_serialization_roundtrip /src/fuzz_serialization_roundtrip.py 9 1168 2 2 0 24 fuzz_serialization_roundtrip.py
fuzz_unpack_roundtrip /src/fuzz_unpack_roundtrip.py 10 1201 2 2 0 27 fuzz_unpack_roundtrip.py

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

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

Runtime coverage analysis

Covered functions
32
Functions that are reachable but not covered
9
Reachable functions
9
Percentage of reachable functions covered
0.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
/ 1
...fuzz_serialization_roundtrip 8

Fuzzer: fuzz_unpack_roundtrip

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 11 100.%
gold [1:9] 0 0.0%
yellow [10:29] 0 0.0%
greenyellow [30:49] 0 0.0%
lawngreen 50+ 0 0.0%
All colors 11 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
10 0 EP call site: 00000 ...fuzz_unpack_roundtrip.ConsumeRandomLengthBufferList

Runtime coverage analysis

Covered functions
32
Functions that are reachable but not covered
10
Reachable functions
10
Percentage of reachable functions covered
0.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
/ 1
...fuzz_unpack_roundtrip 9

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
ipykernel.kernelapp.IPKernelApp.initialize ipykernel.kernelapp 2 ['N/A', 'N/A'] 5 0 21 3 4 91 0 294 291
ipykernel.ipkernel.IPythonKernel.do_execute ipykernel.ipkernel 8 ['N/A', 'N/A', 'N/A', 'N/A', 'N/A', 'N/A', 'N/A', 'N/A'] 2 0 12 9 7 47 0 148 133
ipykernel.zmqshell.ZMQInteractiveShell._showtraceback ipykernel.zmqshell 4 ['N/A', 'N/A', 'N/A', 'N/A'] 3 0 4 2 4 42 0 135 111
ipykernel.debugger.Debugger.process_request ipykernel.debugger 2 ['N/A', 'N/A'] 5 0 5 7 6 35 0 112 91
ipykernel.kernelspec.InstallIPythonKernelSpecApp.start ipykernel.kernelspec 1 ['N/A'] 4 0 13 3 4 24 0 81 66
ipykernel.iostream.OutStream.__init__ ipykernel.iostream 8 ['N/A', 'N/A', 'N/A', 'N/A', 'N/A', 'N/A', 'N/A', 'N/A'] 3 0 6 7 6 29 2 95 51
ipykernel.kernelbase.Kernel.process_shell_message ipykernel.kernelbase 3 ['N/A', 'N/A', 'N/A'] 1 0 20 12 8 17 0 59 50
ipykernel.eventloops.enable_gui ipykernel.eventloops 2 ['N/A', 'N/A'] 3 0 6 10 7 15 1 55 43
ipykernel.subshell_manager.SubshellManager._process_control_request ipykernel.subshell_manager 3 ['N/A', 'N/A', 'N/A'] 3 0 2 3 4 26 1 84 43
ipykernel.iostream.OutStream.flush ipykernel.iostream 1 ['N/A'] 3 0 5 2 4 17 0 57 39

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

Functions statically reachable by fuzzers
16.0%
78 / 496
Cyclomatic complexity statically reachable by fuzzers
18.0%
291 / 1642

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/fuzz_serialization_roundtrip.py

Dictionary

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


/src/fuzz_unpack_roundtrip.py

Dictionary

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


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
re.search 404 73 18.06% ['fuzz_serialization_roundtrip', 'fuzz_unpack_roundtrip']
traitlets.List.iopub_channel.call_handlers 1736 194 11.17% ['fuzz_serialization_roundtrip', 'fuzz_unpack_roundtrip']
jupyter_core.paths.jupyter_runtime_dir 460 62 13.47% ['fuzz_serialization_roundtrip', 'fuzz_unpack_roundtrip']
zmq.log.handlers.PUBHandler.__init__ 44 22 50.0% ['fuzz_serialization_roundtrip', 'fuzz_unpack_roundtrip']
context.socket 169 66 39.05% ['fuzz_serialization_roundtrip', 'fuzz_unpack_roundtrip']
socket.send_multipart 324 111 34.25% ['fuzz_serialization_roundtrip', 'fuzz_unpack_roundtrip']
zmq.asyncio.Context 94 46 48.93% ['fuzz_serialization_roundtrip', 'fuzz_unpack_roundtrip']
jupyter_client.connect.ConnectionFileMixin.shell.InteractiveTB.stb2text 297 74 24.91% ['fuzz_serialization_roundtrip', 'fuzz_unpack_roundtrip']
jupyter_client.localinterfaces.localhost 202 45 22.27% ['fuzz_serialization_roundtrip', 'fuzz_unpack_roundtrip']
jupyter_client.session.Session.msg 449 130 28.95% ['fuzz_serialization_roundtrip', 'fuzz_unpack_roundtrip']
traitlets.config.configurable.SingletonConfigurable.background_socket.displayhook.session.send 258 61 23.64% ['fuzz_serialization_roundtrip']
inspect.isawaitable 566 6 1.060% ['fuzz_serialization_roundtrip', 'fuzz_unpack_roundtrip']
typing.cast 461 232 50.32% ['fuzz_serialization_roundtrip', 'fuzz_unpack_roundtrip']
manager.list_subshell 384 152 39.58% ['fuzz_serialization_roundtrip', 'fuzz_unpack_roundtrip']
loop.shutdown_asyncgens 287 103 35.88% ['fuzz_serialization_roundtrip', 'fuzz_unpack_roundtrip']
traitlets.config.application.Application.instance 520 144 27.69% ['fuzz_serialization_roundtrip', 'fuzz_unpack_roundtrip']
jupyter_client.kernelspec.KernelSpecManager.install_kernel_spec 216 68 31.48% ['fuzz_serialization_roundtrip', 'fuzz_unpack_roundtrip']
parser.parse_args 817 128 15.66% ['fuzz_serialization_roundtrip', 'fuzz_unpack_roundtrip']
jupyter_client.client.KernelClient.session.msg 338 82 24.26% ['fuzz_serialization_roundtrip', 'fuzz_unpack_roundtrip']

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
[] []
gtk [] []
ipykernel.compiler [] []
inspect [] []
ipykernel.inprocess [] []
gc [] []
collections [] []
ipykernel.inprocess.constants [] []
ipykernel._version [] []
ipykernel.comm.manager [] []
shutil [] []
itertools [] []
gobject [] []
ipykernel.inprocess.channels [] []
zmq [] []
ipykernel.kernelapp [] []
comm [] []
binascii [] []
nest_asyncio [] []
atexit [] []
ipykernel.heartbeat [] []
operator [] []
ipykernel.gui [] []
ipykernel.log [] []
ipykernel.comm.comm [] []
...fuzz_serialization_roundtrip ['fuzz_serialization_roundtrip'] []
threading [] []
traceback [] []
jupyter_core [] []
ipykernel.comm [] []
ipyparallel [] []
ipykernel.inprocess.session [] []
ipykernel [] []
traitlets [] []
ipykernel.jsonutil [] []
argparse [] []
_thread [] []
faulthandler [] []
ipykernel.shellchannel [] []
jupyter_client [] []
ipykernel.gui.gtk3embed [] []
ipykernel.inprocess.manager [] []
signal [] []
uuid [] []
os [] []
ipykernel.iostream [] []
psutil [] []
ipykernel.inprocess.ipkernel [] []
ipykernel.zmqshell [] []
pathlib [] []
ipykernel.debugger [] []
ipykernel.displayhook [] []
IPython [] []
wx [] []
contextvars [] []
zmq_anyio [] []
ipykernel.ipkernel [] []
time [] []
math [] []
gi [] []
[] []
subprocess [] []
ipykernel._eventloop_macos [] []
ipykernel.subshell_manager [] []
appnope [] []
ipykernel.connect [] []
ipykernel.pylab.config [] []
io [] []
re [] []
_pydevd_bundle [] []
ipykernel.control [] []
json [] []
ipykernel.kernelbase [] []
ipykernel.inprocess.blocking [] []
platform [] []
ipykernel.kernelspec [] []
ipykernel.__main__ [] []
asyncio [] []
packaging [] []
tempfile [] []
ipykernel.inprocess.client [] []
...fuzz_unpack_roundtrip ['fuzz_unpack_roundtrip'] []
ipykernel.parentpoller [] []
datetime [] []
ipykernel.pylab.backend_inline [] []
warnings [] []
ipykernel.eventloops [] []
functools [] []
tkinter [] []
ipykernel.inprocess.socket [] []
sys [] []
typing [] []
queue [] []
ipykernel.thread [] []
logging [] []
serialize [] []
ipykernel.embed [] []
atheris [] []
ipykernel.gui.gtkembed [] []
anyio [] []
ctypes [] []
ipykernel.pylab [] []
ipykernel.subshell [] []

Directories in report

Directory

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
fuzz_serialization_roundtrip fuzzerLogFile-fuzz_serialization_roundtrip.data fuzzerLogFile-fuzz_serialization_roundtrip.data.yaml all_cov.json
fuzz_unpack_roundtrip fuzzerLogFile-fuzz_unpack_roundtrip.data fuzzerLogFile-fuzz_unpack_roundtrip.data.yaml all_cov.json