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

Fuzzer details

Fuzzer: fuzz_dumps

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

Call tree overview bitmap:

The distribution of callsites in terms of coloring is
Color Runtime hitcount Callsite count Percentage
red 0 76 39.1%
gold [1:9] 0 0.0%
yellow [10:29] 0 0.0%
greenyellow [30:49] 0 0.0%
lawngreen 50+ 118 60.8%
All colors 194 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
17 108 tomlkit._compat.decode call site: 00108 contextlib.suppress
10 31 tomlkit.items.item call site: 00031 collections.abc.MutableSequence.items
8 152 tomlkit.items.item call site: 00152 tomlkit.items.Date.__init__
8 164 tomlkit.items.Time.__init__ call site: 00164 datetime.datetime.isoformat
7 93 tomlkit.items.item call site: 00093 datetime.time.items
7 144 tomlkit.items.DateTime.__init__ call site: 00144 datetime.datetime.isoformat
6 62 tomlkit.items.AoT.__init__ call site: 00062 tomlkit.items.item
3 43 tomlkit.items.item call site: 00043 .isinstance
3 175 tomlkit.items.Array.as_string call site: 00175 v.value.as_string
1 1 ...fuzz_dumps.test_one_input call site: 00001 fdp.ConsumeInt
1 24 tomlkit.items.item call site: 00024 .isinstance
1 50 tomlkit.items.Table.append call site: 00050 tomlkit.items.item

Runtime coverage analysis

Covered functions
268
Functions that are reachable but not covered
63
Reachable functions
95
Percentage of reachable functions covered
33.68%
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_dumps 4
tomlkit.api 17
tomlkit.items 61
tomlkit._compat 10
tomlkit._utils 7

Fuzzer: fuzz_parser

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

Call tree overview bitmap:

The distribution of callsites in terms of coloring is
Color Runtime hitcount Callsite count Percentage
red 0 147 20.2%
gold [1:9] 0 0.0%
yellow [10:29] 0 0.0%
greenyellow [30:49] 0 0.0%
lawngreen 50+ 578 79.7%
All colors 725 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
17 5 tomlkit._compat.decode call site: 00005 contextlib.suppress
12 444 tomlkit.container.Container._replace_at call site: 00444 tomlkit.items.InlineTable.append
11 413 tomlkit.container.Container._replace_at call site: 00413 tomlkit.container.Container._insert_at
10 254 tomlkit.items.item call site: 00254 datetime.datetime.items
8 327 tomlkit.items.item call site: 00327 tomlkit.items.Date.__init__
8 339 tomlkit.items.Time.__init__ call site: 00339 builtins.list.isoformat
7 297 tomlkit.items.item call site: 00297 datetime.datetime.items
7 319 tomlkit.items.DateTime.__init__ call site: 00319 builtins.list.isoformat
6 272 tomlkit.items.AoT.__init__ call site: 00272 tomlkit.items.item
6 672 tomlkit.parser.Parser._parse_table call site: 00672 tomlkit.items.Table.__init__
5 367 tomlkit.container.Container.append call site: 00367 .isinstance
4 407 tomlkit.container.Container._replace_at call site: 00407 tomlkit.items.SingleKey.__init__

Runtime coverage analysis

Covered functions
267
Functions that are reachable but not covered
112
Reachable functions
211
Percentage of reachable functions covered
46.92%
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_parser 4
tomlkit.parser 100
tomlkit._compat 10
tomlkit.source 10
tomlkit.toml_char 2
tomlkit.items 65
tomlkit._utils 18
tomlkit.container 58