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

Fuzzer details

Fuzzer: bs4_fuzzer

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 270 64.2%
gold [1:9] 0 0.0%
yellow [10:29] 0 0.0%
greenyellow [30:49] 0 0.0%
lawngreen 50+ 150 35.7%
All colors 420 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
66 284 bs4.element.SoupStrainer.search_tag call site: 00284 bs4.element.SoupStrainer._matches
65 216 bs4.element.SoupStrainer._matches call site: 00216 html5lib.treebuilders._base.Node.next_sibling.prefix.string.search
48 95 bs4.element.SoupStrainer._normalize_search_value call site: 00095 bs4.BeautifulSoup.decode
28 144 bs4.BeautifulSoup.decode call site: 00144 bs4.element.SoupStrainer._normalize_search_value
9 29 bs4.builder.TreeBuilderRegistry.lookup call site: 00029 candidate_set.intersection
5 4 ...bs4_fuzzer.TestOneInput call site: 00004 warnings.warn
5 182 bs4.element.ResultSet.__init__ call site: 00182 bs4.element.ResultSet.__init__
5 209 bs4.element.SoupStrainer._matches call site: 00209 bs4.element.SoupStrainer._matches
4 415 bs4.element.Tag.prettify call site: 00415 bs4.element.Tag.decode
3 198 bs4.element.SoupStrainer.search_tag call site: 00198 bs4.element.SoupStrainer._matches
2 10 bs4.BeautifulSoup.__init__ call site: 00010 warnings.warn
2 42 bs4.BeautifulSoup.__init__ call site: 00042 .isinstance

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.
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
...bs4_fuzzer 8
bs4 38
bs4.builder 7
bs4.element 243
bs4.formatter 6
bs4.dammit 1