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

Table of contents

Project overview: quick-xml
High level conclusions
Reachability and coverage overview
Fuzzers overview
Project functions overview
Fuzzer details
Fuzzer: fuzz_target_1
Call tree
Fuzz blockers
Runtime coverage analysis
Files reached
Fuzzer: structured_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
fuzz/fuzz_targets/fuzz_target_1.rs
Dictionary
Fuzzer function priority
fuzz/fuzz_targets/structured_roundtrip.rs
Dictionary
Fuzzer function priority
Runtime coverage analysis
Complex functions with low coverage
Fuzz driver synthesis
New fuzzers
Files and Directories in report
Files in report
Directories in report
Function call coverage
Function in each files in report
Metadata section
Sink analyser for CWEs
Report generation date: 2026-02-26

Project overview: quick-xml

High level conclusions

Reachability and coverage overview

Functions statically reachable by fuzzers
2.0%
27 / 1417
Cyclomatic complexity statically reachable by fuzzers
5.0%
72 / 1493
Runtime code coverage of functions
27.0%
385 / 1417

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_target_1 fuzz/fuzz_targets/fuzz_target_1.rs 75 1399 15 20 0 49 fuzz_target_1.rs
structured_roundtrip fuzz/fuzz_targets/structured_roundtrip.rs 62 1402 15 15 0 24 structured_roundtrip.rs

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_target_1

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 619 89.5%
gold [1:9] 0 0.0%
yellow [10:29] 2 0.28%
greenyellow [30:49] 2 0.28%
lawngreen 50+ 68 9.84%
All colors 691 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
125 82 QName::prefix call site: 00082 NamespaceResolver::push
105 310 from_str_radix call site: 00310 NamespaceResolver::push
89 539 &[u8]::len call site: 00539 NamespaceResolver::push
79 459 parse_number call site: 00459 NamespaceResolver::push
33 3 Reader::from_reader call site: 00003 round_trip
28 38 Reader::from_str call site: 00038 NsReader::read_resolved_event
27 250 Option::len call site: 00250 NamespaceResolver::push
25 278 Attribute::normalized_value call site: 00278 normalize_attribute_value
22 420 Writer::write_wrapped call site: 00420 Writer::write_wrapped
20 229 name_len call site: 00229 NamespaceResolver::push
20 632 BytesDecl::version call site: 00632
17 673 BytesDecl::xml_version call site: 00673 round_trip

Runtime coverage analysis

Covered functions
296
Functions that are reachable but not covered
44
Reachable functions
75
Percentage of reachable functions covered
41.33%
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
fuzz/fuzz_targets/fuzz_target_1.rs 28
src/reader/ns_reader.rs 41
src/lib.rs 3
src/name.rs 44
src/se/mod.rs 5
src/utils.rs 11
src/events/mod.rs 22
tests/reader-namespaces.rs 5
tests/serde_helpers/mod.rs 5
src/events/attributes.rs 14
tests/serde-de-enum.rs 16
tests/reader-dtd.rs 1
src/escape.rs 36
tests/writer-indentation.rs 7
src/writer.rs 34
src/encoding.rs 14
tests/roundtrip.rs 1
tests/html.rs 11
tests/escape.rs 19
tests/writer.rs 20

Fuzzer: structured_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 354 70.3%
gold [1:9] 6 1.19%
yellow [10:29] 3 0.59%
greenyellow [30:49] 0 0.0%
lawngreen 50+ 140 27.8%
All colors 503 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
59 250 NsReader::process_event call site: 00250 NsReader::read_resolved_event
50 192 NamespaceResolver::pop call site: 00192 read_event_impl
43 126 Reader::from_str call site: 00126 NsReader::read_resolved_event
23 82 fuzz_round_trip call site: 00082 SpecIter::next
21 36 Writer::write_wrapped call site: 00036 Writer::write_wrapped
19 403 ElementWriter::write_text_content call site: 00403 Writer::write_wrapped
15 430 ElementWriter::write_text_content call site: 00430 read_to_end
14 67 fuzz_round_trip call site: 00067 Decoder::decode_into
12 177 NamespaceResolver::set_level call site: 00177
11 9 fuzz_round_trip call site: 00009 decode_into
11 363 BytesStart::push_attr call site: 00363 Decoder::decode_into
10 21 name_len call site: 00021 Writer::write_wrapped

Runtime coverage analysis

Covered functions
348
Functions that are reachable but not covered
28
Reachable functions
62
Percentage of reachable functions covered
54.84%
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
fuzz/fuzz_targets/structured_roundtrip.rs 30
src/se/mod.rs 2
src/utils.rs 9
src/writer.rs 37
src/encoding.rs 12
tests/roundtrip.rs 1
src/events/mod.rs 20
tests/html.rs 11
src/name.rs 44
tests/serde-de-enum.rs 16
tests/serde_helpers/mod.rs 5
src/reader/ns_reader.rs 47
src/lib.rs 3
tests/reader-namespaces.rs 5
src/events/attributes.rs 5

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

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

Functions statically reachable by fuzzers
2.0%
27 / 1417
Cyclomatic complexity statically reachable by fuzzers
5.0%
72 / 1493

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.

fuzz/fuzz_targets/fuzz_target_1.rs

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=['QName::prefix', 'from_str_radix', '&[u8]::len', 'parse_number', 'Reader::from_reader', 'Reader::from_str', 'Option::len', 'Attribute::normalized_value', 'Writer::write_wrapped', 'name_len']

fuzz/fuzz_targets/structured_roundtrip.rs

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=['NsReader::process_event', 'NamespaceResolver::pop', 'Reader::from_str', 'fuzz_round_trip', 'Writer::write_wrapped', 'ElementWriter::write_text_content', 'NamespaceResolver::set_level']

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
memchr::arch::generic::memchr::Onecore::core_arch::x86::__m128i::find_raw 63 30 47.61%
memchr::arch::generic::memchr::Threecore::core_arch::x86::__m128i::find_raw 63 30 47.61%

Fuzz driver synthesis

New fuzzers

The below fuzzers are templates and suggestions for how to target the set of optimal functions above

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
/src/quick-xml/tests/async-tokio.rs [] []
/src/quick-xml/src/se/element.rs [] []
/src/quick-xml/tests/reader.rs [] []
/src/quick-xml/src/de/mod.rs [] []
/src/quick-xml/src/reader/mod.rs [] []
/src/quick-xml/src/de/var.rs [] []
/src/quick-xml/src/se/mod.rs ['fuzz_target_1', 'structured_roundtrip'] ['fuzz_target_1', 'structured_roundtrip']
/src/quick-xml/tests/reader-namespaces.rs ['fuzz_target_1', 'structured_roundtrip'] ['fuzz_target_1', 'structured_roundtrip']
/src/quick-xml/src/writer/async_tokio.rs [] []
/src/quick-xml/compare/benches/serde.rs [] []
/src/quick-xml/src/se/text.rs [] []
/src/quick-xml/src/name.rs ['fuzz_target_1', 'structured_roundtrip'] ['fuzz_target_1', 'structured_roundtrip']
/src/quick-xml/test-gen/src/main.rs [] []
/src/quick-xml/src/se/simple_type.rs [] []
/src/quick-xml/fuzz/fuzz_targets/fuzz_target_1.rs ['fuzz_target_1'] []
/src/quick-xml/tests/serde-issues.rs [] []
/src/quick-xml/src/writer.rs ['fuzz_target_1', 'structured_roundtrip'] ['fuzz_target_1', 'structured_roundtrip']
/src/quick-xml/src/se/key.rs [] []
/src/quick-xml/tests/roundtrip.rs ['fuzz_target_1', 'structured_roundtrip'] ['fuzz_target_1', 'structured_roundtrip']
/src/quick-xml/tests/escape.rs ['fuzz_target_1'] []
/src/quick-xml/tests/serde-de-xsi.rs [] []
/src/quick-xml/tests/serde-de-seq.rs [] []
/src/quick-xml/src/parser/dtd.rs [] []
/src/quick-xml/tests/reader-read-text.rs [] []
/src/quick-xml/tests/writer.rs ['fuzz_target_1'] ['fuzz_target_1']
/src/quick-xml/tests/fuzzing.rs [] []
/src/quick-xml/src/de/key.rs [] []
/src/quick-xml/src/events/mod.rs ['fuzz_target_1', 'structured_roundtrip'] ['fuzz_target_1', 'structured_roundtrip']
/src/quick-xml/src/utils.rs ['fuzz_target_1', 'structured_roundtrip'] ['fuzz_target_1', 'structured_roundtrip']
/src/quick-xml/src/lib.rs ['fuzz_target_1', 'structured_roundtrip'] ['fuzz_target_1', 'structured_roundtrip']
/src/quick-xml/benches/macrobenches.rs [] []
/src/quick-xml/src/reader/slice_reader.rs [] []
/src/quick-xml/tests/reader-dtd.rs ['fuzz_target_1'] []
/src/quick-xml/src/reader/async_tokio.rs [] []
/src/quick-xml/src/events/attributes.rs ['fuzz_target_1', 'structured_roundtrip'] ['fuzz_target_1', 'structured_roundtrip']
/src/quick-xml/tests/html.rs ['fuzz_target_1', 'structured_roundtrip'] ['fuzz_target_1', 'structured_roundtrip']
/src/quick-xml/src/de/attributes.rs [] []
/src/quick-xml/examples/read_texts.rs [] []
/src/quick-xml/src/de/simple_type.rs [] []
/src/quick-xml/src/reader/buffered_reader.rs [] []
/src/quick-xml/tests/encodings.rs [] []
/src/quick-xml/src/parser/pi.rs [] []
/src/quick-xml/tests/serde-de-enum.rs ['fuzz_target_1', 'structured_roundtrip'] ['fuzz_target_1', 'structured_roundtrip']
/src/quick-xml/src/se/content.rs [] []
/src/quick-xml/src/parser/comment.rs [] []
/src/quick-xml/examples/flattened_enum.rs [] []
/src/quick-xml/benches/microbenches.rs [] []
/src/quick-xml/examples/read_nodes.rs [] []
/src/quick-xml/src/errors.rs [] []
/src/quick-xml/examples/custom_entities.rs [] []
/src/quick-xml/src/encoding.rs ['fuzz_target_1', 'structured_roundtrip'] ['fuzz_target_1', 'structured_roundtrip']
/src/quick-xml/tests/issues.rs [] []
/src/quick-xml/src/de/resolver.rs [] []
/src/quick-xml/src/serde_helpers.rs [] []
/src/quick-xml/compare/benches/low-level.rs [] []
/src/quick-xml/tests/writer-indentation.rs ['fuzz_target_1'] []
/src/quick-xml/tests/reader-errors.rs [] []
/src/quick-xml/src/reader/ns_reader.rs ['fuzz_target_1', 'structured_roundtrip'] ['fuzz_target_1', 'structured_roundtrip']
/src/quick-xml/tests/reader-references.rs [] []
/src/quick-xml/tests/helpers/mod.rs [] []
/src/quick-xml/tests/reader-attributes.rs [] []
/src/quick-xml/src/escape.rs ['fuzz_target_1'] ['fuzz_target_1']
/src/quick-xml/src/parser/element.rs [] []
/src/quick-xml/src/reader/state.rs [] []
/src/quick-xml/src/de/map.rs [] []
/src/quick-xml/tests/reader-config.rs [] []
/src/quick-xml/fuzz/fuzz_targets/structured_roundtrip.rs ['structured_roundtrip'] ['structured_roundtrip']
/src/quick-xml/src/de/text.rs [] []
/src/quick-xml/tests/serde-de.rs [] []

Directories in report

Directory
/src/quick-xml/src/parser/
/src/quick-xml/tests/
/src/quick-xml/src/se/
/src/quick-xml/test-gen/src/
/src/quick-xml/benches/
/src/quick-xml/src/reader/
/src/quick-xml/fuzz/fuzz_targets/
/src/quick-xml/tests/helpers/
/src/quick-xml/src/writer/
/src/quick-xml/src/
/src/quick-xml/compare/benches/
/src/quick-xml/examples/
/src/quick-xml/src/de/
/src/quick-xml/src/events/

Function call coverage

This section shows a list of 3rd party function calls and their relative coverage information. By static analysis of the target project code, all of the 3rd party function call and their caller information, including the source file and line number that initiate the call are captured. The caller source code file and line number are shown in column 2 while column 1 is the function name of the 3rd party function call. Each occurrent of the 3rd party function call will occuply a separate row. Column 3 of each row indicate if the 3rd party call in the source file line is unreachable. Column 4 lists all fuzzers that have covered that particular system call in that specific location (source file and line)during their dynamic fuzzing.

Function in each files in report

Target sink Callsite location Reached by fuzzer Covered by Fuzzers

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_target_1 fuzzerLogFile-fuzz_target_1.data fuzzerLogFile-fuzz_target_1.data.yaml fuzz_target_1.covreport
structured_roundtrip fuzzerLogFile-structured_roundtrip.data fuzzerLogFile-structured_roundtrip.data.yaml structured_roundtrip.covreport

Sink analyser for CWEs

No sink functions/methods found in the target project.