Report generation date: 2026-02-09

Project overview: pyparsing

High level conclusions

The runtime code coverage of fuzz_parse covers 24.09% of its statically reachable code. This means there is some place that blocks the fuzzer to continue exploring more code at run time.

Reachability and coverage overview

Functions statically reachable by fuzzers

32 / 476

Cyclomatic complexity statically reachable by fuzzers

106 / 1681

Runtime code coverage of functions

219 / 476

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_parse	/src/fuzz_parse.py	83	965	9	7	31	256	fuzz_parse.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_parse

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 141 40.4%

gold [1:9] 0 0.0%

yellow [10:29] 0 0.0%

greenyellow [30:49] 0 0.0%

lawngreen 50+ 208 59.5%

All colors 349 100

Color	Runtime hitcount	Callsite count	Percentage
red	0	141	40.4%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	208	59.5%
All colors	349	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
28	88	pyparsing.core._trim_arity	call site: 00088	pyparsing.core.token_map.pa
25	48	pyparsing.core.Empty.__init__	call site: 00048	pyparsing.helpers.match_previous_literal.copy_token_to_repeater
18	119	pyparsing.core.SkipTo.__init__	call site: 00119	pyparsing.helpers.match_previous_literal.copy_token_to_repeater
17	141	pyparsing.core.SkipTo._update_ignorer	call site: 00141	pyparsing.core.Combine.ignore
8	163	pyparsing.core.ParserElement.set_whitespace_chars	call site: 00163	pyparsing.core.token_map.pa
6	12	pyparsing.results.ParseResults.__iter__	call site: 00012	pyparsing.util._flatten
6	26	...fuzz_parse.dict_parse_generator	call site: 00026	warnings.warn
5	6	...fuzz_parse.dict_parse_generator	call site: 00006	pyparsing.util._flatten
5	20	...fuzz_parse.dict_parse_generator	call site: 00020	pyparsing.util.col
5	38	...fuzz_parse.dict_parse_generator	call site: 00038	pyparsing.helpers.match_previous_expr.copy_token_to_repeater.must_match_these_tokens
4	74	pyparsing.core.ParserElement.set_parse_action	call site: 00074	pyparsing.util._to_pep8_name
3	33	...fuzz_parse.dict_parse_generator	call site: 00033	pyparsing.util.col

Runtime coverage analysis

Covered functions

235

Functions that are reachable but not covered

63

Reachable functions

83

Percentage of reachable functions covered

24.1%

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_parse	29
pyparsing.core	47
pyparsing.helpers	28
pyparsing.util	12
pyparsing.results	1
pyparsing.tools.cvt_pyparsing_pep8_names	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	instr count	bb count	cyclomatic complexity	Reachable functions	Incoming references	total cyclomatic complexity	Unreached complexity
`pyparsing.core.ParserElement.run_tests`	pyparsing.core	15	['N/A', 'N/A', 'N/A', 'N/A', 'N/A', 'N/A', 'N/A', 'N/A', 'N/A', 'N/A', 'N/A', 'N/A', 'N/A', 'N/A', 'N/A']	12	17	13	8	229	1	734	516
`pyparsing.diagram.to_railroad`	pyparsing.diagram	6	['N/A', 'N/A', 'N/A', 'N/A', 'N/A', 'N/A']	11	5	5	5	201	1	662	117
`pyparsing.helpers.one_of`	pyparsing.helpers	5	['N/A', 'N/A', 'N/A', 'N/A', 'N/A']	11	6	11	7	206	1	656	58
`pyparsing.testing.pyparsing_test.reset_pyparsing_context.restore`	pyparsing.testing	1	['N/A']	4	5	2	4	27	1	87	57
`pyparsing.helpers._makeTags`	pyparsing.helpers	4	['N/A', 'N/A', 'N/A', 'N/A']	8	3	2	4	117	4	366	57
`pyparsing.core.Each.parseImpl`	pyparsing.core	4	['N/A', 'N/A', 'N/A', 'N/A']	4	10	8	6	23	0	78	42
`pyparsing.core.Word.__init__`	pyparsing.core	9	['N/A', 'N/A', 'N/A', 'N/A', 'N/A', 'N/A', 'N/A', 'N/A', 'N/A']	3	1	20	11	22	0	79	40

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

Functions statically reachable by fuzzers

97 / 476

Cyclomatic complexity statically reachable by fuzzers

384 / 1681

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_parse.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=['pyparsing.core._trim_arity', 'pyparsing.core.Empty.__init__', 'pyparsing.core.SkipTo.__init__', 'pyparsing.core.SkipTo._update_ignorer', 'pyparsing.core.ParserElement.set_whitespace_chars', 'pyparsing.results.ParseResults.__iter__', '...fuzz_parse.dict_parse_generator']

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
pyparsing.core.ParserElement._parseNoCache	61	24	39.34%	['fuzz_parse']
pyparsing.core.ParserElement._parseCache	36	1	2.777%	['fuzz_parse']
pyparsing.core.ParserElement.scan_string	42	0	0.0%	[]
pyparsing.core.ParserElement.run_tests	76	0	0.0%	[]
pyparsing.core.QuotedString.__init__	58	0	0.0%	[]
pyparsing.core.Or.parseImpl	61	0	0.0%	[]
pyparsing.core.Each.parseImpl	55	0	0.0%	[]
pyparsing.core.SkipTo.parseImpl	35	2	5.714%	['fuzz_parse']
pyparsing.core.Forward.parseImpl	45	0	0.0%	[]
pyparsing.helpers.one_of	50	0	0.0%	[]
pyparsing.helpers.infix_notation._FB.parseImpl	69	0	0.0%	[]
pyparsing.helpers.indentedBlock.checkUnindent	32	14	43.75%	['fuzz_parse']
pyparsing.exceptions.ParseBaseException.explain_exception	35	0	0.0%	[]
pyparsing.util.make_compressed_re.get_suffixes_from_common_prefixes	44	0	0.0%	[]
pyparsing.testing.pyparsing_test.with_line_numbers	41	0	0.0%	[]

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
	[]	[]
pyparsing.diagram	[]	[]
argparse	[]	[]
types	[]	[]
datetime	[]	[]
traceback	[]	[]
...fuzz_parse	['fuzz_parse']	[]
pyparsing.util	['fuzz_parse']	[]
pyparsing.ai.show_best_practices	[]	[]
pyparsing.actions	[]	[]
typing	[]	[]
io	[]	[]
importlib	[]	[]
pyparsing.results	['fuzz_parse']	[]
contextlib	[]	[]
inspect	[]	[]
	[]	[]
warnings	[]	[]
pathlib	[]	[]
itertools	[]	[]
atheris	[]	[]
pyparsing.exceptions	[]	[]
pyparsing.testing	[]	[]
threading	[]	[]
operator	[]	[]
pyparsing.common	[]	[]
sys	[]	[]
os	[]	[]
pyparsing.helpers	['fuzz_parse']	[]
re	[]	[]
pyparsing.tools.cvt_pyparsing_pep8_names	['fuzz_parse']	[]
core_builtin_exprs	[]	[]
pyparsing.warnings	[]	[]
pyparsing.core	['fuzz_parse']	[]
abc	[]	[]
railroad	[]	[]
functools	[]	[]
unittest	[]	[]
difflib	[]	[]
collections	[]	[]
pyparsing.tools	[]	[]
pyparsing.ai.show_best_practices.__main__	[]	[]
pyparsing.ai	[]	[]
pyparsing.unicode	[]	[]
jinja2	[]	[]
pyparsing	[]	[]

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_parse fuzzerLogFile-fuzz_parse.data fuzzerLogFile-fuzz_parse.data.yaml all_cov.json

Table of contents

Project overview: pyparsing

High level conclusions

Reachability and coverage overview

Fuzzers overview

Project functions overview

Fuzzer details

Fuzzer: fuzz_parse

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_parse.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