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

Table of contents

Project overview: rich
High level conclusions
Reachability and coverage overview
Fuzzers overview
Project functions overview
Fuzzer details
Fuzzer: fuzz_markdown
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_markdown.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-11

Project overview: rich

High level conclusions

Reachability and coverage overview

Functions statically reachable by fuzzers
16.0%
139 / 857
Cyclomatic complexity statically reachable by fuzzers
18.0%
531 / 2929
Runtime code coverage of functions
36.0%
309 / 857

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
fuzz_markdown /src/fuzz_markdown.py 317 1204 11 27 306 1063 fuzz_markdown.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_markdown

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 476 61.0%
gold [1:9] 0 0.0%
yellow [10:29] 0 0.0%
greenyellow [30:49] 0 0.0%
lawngreen 50+ 304 38.9%
All colors 780 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
77 452 rich.console.Console.render call site: 00452 rich.pretty.pretty_repr
33 131 rich.style.Style.__init__ call site: 00131 rich.style.Style.normalize
28 550 rich.text.Text.render call site: 00550 rich.console.Console.render
20 607 rich.color.Color.from_triplet call site: 00607 rich.text.Text.with_indent_guides
19 736 rich.containers.Lines.justify call site: 00736 rich.text.Text.join
16 390 rich.text.Text.stylize call site: 00390 rich.syntax.Syntax._apply_stylized_ranges
15 58 rich.text.Text.__init__ call site: 00058 rich.text.Text.append
14 592 rich.ansi.AnsiDecoder.decode_line call site: 00592 rich.color.Color.from_rgb
14 672 rich.text.Text.expand_tabs call site: 00672 rich.text.Text.split
13 187 rich.console.Console._collect_renderables call site: 00187 rich.console.Console._collect_renderables.check_text
13 260 rich.segment.Segment.split_and_crop_lines call site: 00260 rich.segment.Segment.adjust_line_length
12 421 rich.markdown.Markdown.__rich_console__ call site: 00421 rich.markdown.MarkdownContext.on_text

Runtime coverage analysis

Covered functions
390
Functions that are reachable but not covered
219
Reachable functions
317
Percentage of reachable functions covered
30.91%
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_markdown 6
rich.markdown 32
rich.console 70
rich._windows 4
rich._win32_console 3
rich.protocol 9
rich.markup 28
rich.text 62
rich.control 4
rich._emoji_replace 1
rich.style 21
rich.color 12
rich._loop 2
rich.pretty 50
rich.layout 15
rich.segment 8
rich.cells 7
rich.panel 19
rich.padding 3
rich.measure 7
rich.syntax 35
rich.ansi 26
rich._pick 1
rich.containers 18
rich._wrap 9
rich.constrain 3

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
rich.console.PagerContext.__exit__ rich.console 4 ['N/A', 'N/A', 'N/A', 'N/A'] 5 0 2 3 4 70 0 230 197
rich.table.Table.__rich_console__ rich.table 3 ['N/A', 'N/A', 'N/A'] 8 0 4 4 5 126 0 431 134
rich.logging.RichHandler.emit rich.logging 2 ['N/A', 'N/A'] 7 0 4 4 5 132 0 437 127
rich.traceback.Traceback.__rich_console__.render_stack rich.traceback 2 ['N/A', 'N/A'] 8 0 11 6 5 110 2 363 116
rich.console.Console.export_svg rich.console 7 ['N/A', 'N/A', 'N/A', 'N/A', 'N/A', 'N/A', 'N/A'] 4 0 4 7 6 56 1 188 75
rich._inspect.Inspect._render rich._inspect 1 ['N/A'] 4 0 19 16 9 97 1 322 71
rich.progress.Progress.track rich.progress 7 ['N/A', 'N/A', 'N/A', 'N/A', 'N/A', 'N/A', 'N/A'] 4 0 6 3 4 25 1 84 66
rich.syntax.Syntax._get_syntax rich.syntax 3 ['N/A', 'N/A', 'N/A'] 7 0 13 13 8 107 1 359 49
rich.progress.ProgressColumn.__call__ rich.progress 2 ['N/A', 'N/A'] 6 0 1 2 4 80 0 267 48
rich.live.Live.start rich.live 2 ['N/A', 'N/A'] 4 0 7 5 5 24 6 85 41

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

Functions statically reachable by fuzzers
32.0%
273 / 857
Cyclomatic complexity statically reachable by fuzzers
35.0%
1033 / 2929

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_markdown.py

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=['rich.console.Console.render', 'rich.style.Style.__init__', 'rich.text.Text.render', 'rich.color.Color.from_triplet', 'rich.containers.Lines.justify', 'rich.text.Text.stylize', 'rich.text.Text.__init__', 'rich.ansi.AnsiDecoder.decode_line', 'rich.text.Text.expand_tabs', 'rich.console.Console._collect_renderables']

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
rich.console.Console._write_buffer 49 10 20.40% ['fuzz_markdown']
rich.console.Console.export_html 36 0 0.0% []
rich.console.Console.export_svg.get_svg_style 42 0 0.0% []
rich.console.Console.export_svg.make_tag.stringify 47 0 0.0% []
rich._inspect.Inspect._render.safe_getattr 60 1 1.666% ['fuzz_markdown']
rich.panel.Panel.__rich_console__.align_text 50 25 50.0% ['fuzz_markdown']
rich.table.Table._calculate_column_widths 32 11 34.37% ['fuzz_markdown']
rich.pretty.traverse._traverse.iter_rich_args 61 0 0.0% ['fuzz_markdown']
rich.pretty.traverse._traverse.iter_attrs 89 0 0.0% ['fuzz_markdown']
rich.segment.Segment.divide 47 2 4.255% ['fuzz_markdown']
rich._log_render.LogRender.__call__ 35 1 2.857% ['fuzz_markdown']
rich.markup.render.pop_style 51 1 1.960% ['fuzz_markdown']
rich.style.Style.__str__ 43 0 0.0% []
rich.style.Style.parse 39 2 5.128% ['fuzz_markdown']
rich.rule.Rule.__rich_console__ 40 6 15.0% ['fuzz_markdown']
rich.color.Color.downgrade 38 6 15.78% ['fuzz_markdown']
rich.box.Box.get_row 32 16 50.0% ['fuzz_markdown']
data.items 304 117 38.48% ['fuzz_markdown']
rich.syntax.Syntax._get_syntax 62 28 45.16% ['fuzz_markdown']
pygments.lexers.get_lexer_by_name 192 59 30.72% ['fuzz_markdown']
rich.containers.Lines.justify 38 16 42.10% ['fuzz_markdown']

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
[] []
math [] []
operator [] []
fractions [] []
platform [] []
textwrap [] []
colorsys [] []
rich._win32_console ['fuzz_markdown'] []
rich.live_render [] []
logging [] []
functools [] []
[] []
rich._ratio [] []
rich.styled [] []
rich.prompt [] []
rich.tree [] []
argparse [] []
ast [] []
rich.style ['fuzz_markdown'] []
rich._emoji_replace ['fuzz_markdown'] []
rich.scope [] []
traceback [] []
abc [] []
typing [] []
rich._stack [] []
itertools [] []
ipywidgets [] []
pygments [] []
pty [] []
rich.pretty ['fuzz_markdown'] []
rich.color ['fuzz_markdown'] []
rich._export_format [] []
rich._windows_renderer [] []
get_console [] []
rich.repr [] []
attr [] []
rich.palette [] []
rich.terminal_theme [] []
json [] []
rich.cells ['fuzz_markdown'] []
rich.panel ['fuzz_markdown'] []
threading [] []
rich._cell_widths [] []
rich.abc [] []
ctypes [] []
rich.file_proxy [] []
io [] []
marshal [] []
rich._extension [] []
rich._wrap ['fuzz_markdown'] []
rich.progress [] []
rich.filesize [] []
rich.syntax ['fuzz_markdown'] []
IPython [] []
re [] []
rich.ansi ['fuzz_markdown'] []
dataclasses [] []
rich.bar [] []
rich.constrain ['fuzz_markdown'] []
rich.theme [] []
rich._spinners [] []
rich.table [] []
rich._inspect [] []
rich.progress_bar [] []
warnings [] []
rich.text ['fuzz_markdown'] []
rich.highlighter [] []
pathlib [] []
rich.errors [] []
rich.containers ['fuzz_markdown'] []
rich.box [] []
os [] []
rich.padding ['fuzz_markdown'] []
collections [] []
markdown_it [] []
rich._emoji_codes [] []
rich.themes [] []
rich.measure ['fuzz_markdown'] []
rich.screen [] []
rich._log_render [] []
rich.json [] []
getpass [] []
rich.markdown ['fuzz_markdown'] []
rich.rule [] []
rich.live [] []
rich._loop ['fuzz_markdown'] []
...fuzz_markdown ['fuzz_markdown'] []
atheris [] []
rich.emoji [] []
rich._null_file [] []
rich.jupyter [] []
rich.status [] []
rich.diagnose [] []
rich.console ['fuzz_markdown'] []
datetime [] []
rich.logging [] []
zlib [] []
rich.align [] []
rich.pager [] []
time [] []
rich.color_triplet [] []
rich.columns [] []
pydoc [] []
rich.spinner [] []
sys [] []
rich.traceback [] []
linecache [] []
rich._timer [] []
random [] []
rich._pick ['fuzz_markdown'] []
rich.control ['fuzz_markdown'] []
contextlib [] []
rich.protocol ['fuzz_markdown'] []
rich [] []
rich.__main__ [] []
rich._palettes [] []
rich.layout ['fuzz_markdown'] []
inspect [] []
rich._fileno [] []
rich.region [] []
rich.markup ['fuzz_markdown'] []
rich._windows ['fuzz_markdown'] []
html [] []
configparser [] []
rich.default_styles [] []
rich.segment ['fuzz_markdown'] []

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_markdown fuzzerLogFile-fuzz_markdown.data fuzzerLogFile-fuzz_markdown.data.yaml all_cov.json