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

Fuzzer details

Fuzzer: fuzz_argparse

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 0 0.0%
gold [1:9] 0 0.0%
yellow [10:29] 0 0.0%
greenyellow [30:49] 0 0.0%
lawngreen 50+ 16 100.%
All colors 16 100

Runtime coverage analysis

Covered functions
109
Functions that are reachable but not covered
6
Reachable functions
7
Percentage of reachable functions covered
14.29%
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_argparse 6

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
absl.app.run absl.app 3 ['N/A', 'N/A', 'N/A'] 9 0 10 2 4 120 2 394 391
absl.flags._flagvalues.FlagValues.__call__ absl.flags._flagvalues 3 ['N/A', 'N/A', 'N/A'] 3 0 3 2 4 62 0 214 184
absl.flags._flag.Flag._create_xml_dom_element absl.flags._flag 4 ['N/A', 'N/A', 'N/A', 'N/A'] 3 0 10 5 5 30 0 95 80
absl.flags._defines.DEFINE_flag absl.flags._defines 4 ['N/A', 'N/A', 'N/A', 'N/A'] 3 0 4 3 4 22 17 71 62
absl.logging.PythonHandler.start_logging_to_file absl.logging 3 ['N/A', 'N/A', 'N/A'] 3 0 3 2 4 22 3 72 48
absl.testing.absltest.TestCase.assertMappingEqual absl.testing.absltest 5 ['N/A', 'N/A', 'N/A', 'N/A', 'N/A'] 2 0 9 9 7 17 2 58 46
absl.testing.parameterized._ParameterizedTestIter.__iter__.make_bound_param_test absl.testing.parameterized 1 ['N/A'] 3 0 0 10 7 15 1 53 44
absl.flags._flag.Flag.__init__ absl.flags._flag 13 ['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'] 4 0 1 2 4 22 8 75 42
absl.logging.PythonHandler.emit absl.logging 2 ['N/A', 'N/A'] 2 0 8 5 5 17 1 57 42
absl.testing.xml_reporter._TextAndXMLTestResult.addSubTest absl.testing.xml_reporter 4 ['N/A', 'N/A', 'N/A', 'N/A'] 4 0 2 2 4 18 0 60 42

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

Functions statically reachable by fuzzers
20.0%
105 / 518
Cyclomatic complexity statically reachable by fuzzers
23.0%
399 / 1747

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 Fuzzers runtime hit Func lines hit % I Count BB Count Cyclomatic complexity Functions reached Reached by functions Accumulated cyclomatic complexity Undiscovered complexity

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
[] []
copy [] []
absl.testing._pretty_print_reporter [] []
threading [] []
atexit [] []
xml [] []
tempfile [] []
inspect [] []
struct [] []
argparse [] []
os [] []
absl.flags [] []
collections [] []
shlex [] []
difflib [] []
re [] []
fcntl [] []
getpass [] []
absl.flags._validators_classes [] []
subprocess [] []
socket [] []
absl.flags._exceptions [] []
textwrap [] []
urllib [] []
[] []
warnings [] []
shutil [] []
absl.flags._validators [] []
absl.testing.xml_reporter [] []
faulthandler [] []
absl.testing.absltest [] []
timeit [] []
time [] []
unittest [] []
random [] []
absl.flags._helpers [] []
functools [] []
datetime [] []
absl.flags.argparse_flags [] []
absl.testing.parameterized [] []
absl.flags._defines [] []
csv [] []
traceback [] []
absl.testing._bazelize_command [] []
json [] []
absl.flags._flagvalues [] []
absl.logging.converter [] []
itertools [] []
absl.testing [] []
ctypes [] []
atheris [] []
sys [] []
absl.flags._flag [] []
absl.flags._argument_parser [] []
typing [] []
logging [] []
dataclasses [] []
absl.command_name [] []
absl.app [] []
profile [] []
absl.testing.flagsaver [] []
pdb [] []
io [] []
absl [] []
...fuzz_argparse ['fuzz_argparse'] []
absl.logging [] []
contextlib [] []

Directories in report

Directory