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

Fuzzer details

Fuzzer: fuzz_itertoolz

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 41 22.7%
gold [1:9] 0 0.0%
yellow [10:29] 0 0.0%
greenyellow [30:49] 0 0.0%
lawngreen 50+ 139 77.2%
All colors 180 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
13 66 ...fuzz_itertoolz.TestOneInput call site: 00066 .callable
4 158 toolz.sandbox.core.EqualityHashKey.__init__ call site: 00158 .isinstance
4 169 toolz.sandbox.parallel.fold call site: 00169 .iter
2 89 ...fuzz_itertoolz.TestOneInput call site: 00089 .reversed
2 101 ...fuzz_itertoolz.TestOneInput call site: 00101 fdp.ConsumeUnicodeNoSurrogates
2 117 ...fuzz_itertoolz.TestOneInput call site: 00117 ...fuzz_itertoolz.ConsumeDictionary
2 120 ...fuzz_itertoolz.TestOneInput call site: 00120 ...fuzz_itertoolz.ConsumeDictionaryWithList
2 129 ...fuzz_itertoolz.TestOneInput call site: 00129 ...fuzz_itertoolz.ConsumeDictionary
1 18 ...fuzz_itertoolz.TestOneInput call site: 00018 fdp.ConsumeUnicodeNoSurrogates
1 27 ...fuzz_itertoolz.TestOneInput call site: 00027 toolz.join
1 29 ...fuzz_itertoolz.TestOneInput call site: 00029 toolz.join
1 31 ...fuzz_itertoolz.TestOneInput call site: 00031 toolz.join

Runtime coverage analysis

Covered functions
Functions that are reachable but not covered
Reachable functions
Percentage of reachable functions covered
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.
Function name source code lines source lines hit percentage hit

Files reached

filename functions hit
/ 1
...fuzz_itertoolz 48
toolz.functoolz 8
toolz.sandbox.core 10
toolz.itertoolz 7
toolz.sandbox.parallel 5