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

Table of contents

Project overview: distlib
High level conclusions
Reachability and coverage overview
Fuzzers overview
Project functions overview
Fuzzer details
Fuzzer: fuzz_marker
Call tree
Fuzz blockers
Runtime coverage analysis
Files reached
Fuzzer: fuzz_metadata
Call tree
Fuzz blockers
Runtime coverage analysis
Files reached
Analyses and suggestions
Optimal target analysis
Remaining optimal interesting functions
All functions overview
Runtime coverage analysis
Complex functions with low coverage
Files and Directories in report
Files in report
Directories in report
Metadata section
Function call coverage
Function in each files in report
Report generation date: 2023-09-25

Project overview: distlib

High level conclusions

Reachability and coverage overview

Functions statically reachable by fuzzers
8.0%
44 / 575
Cyclomatic complexity statically reachable by fuzzers
8.0%
176 / 2097
Runtime code coverage of functions
16.0%
91 / 575

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_marker /src/fuzz_marker.py 52 1285 7 5 41 168 fuzz_marker.py
fuzz_metadata /src/fuzz_metadata.py 94 1242 11 4 98 316 fuzz_metadata.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 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_marker

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 36 36.0%
gold [1:9] 0 0.0%
yellow [10:29] 0 0.0%
greenyellow [30:49] 0 0.0%
lawngreen 50+ 64 64.0%
All colors 100 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 77 distlib.version.Version.__init__ call site: 00077 distlib.version._legacy_key
10 65 distlib.version.Version.__init__ call site: 00065 distlib.version._semantic_key
7 92 distlib.version.Version.__init__ call site: 00092 distlib.markers._get_versions
4 38 distlib.markers.Evaluator.evaluate call site: 00038 distlib.version.Version.__init__
1 29 distlib.markers.interpret call site: 00029 context.update
1 54 distlib.version._pep_440_key call site: 00054 .int

Runtime coverage analysis

Covered functions
98
Functions that are reachable but not covered
41
Reachable functions
52
Percentage of reachable functions covered
21.15%
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_marker 3
distlib.markers 11
distlib.util 12
distlib.version 29

Fuzzer: fuzz_metadata

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 67 36.0%
gold [1:9] 0 0.0%
yellow [10:29] 0 0.0%
greenyellow [30:49] 0 0.0%
lawngreen 50+ 119 63.9%
All colors 186 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 64 distlib.version.Version.__init__ call site: 00064 distlib.version._legacy_key
10 53 distlib.version.Version.__init__ call site: 00053 distlib.version._semantic_key
10 105 distlib.metadata.LegacyMetadata.__init__ call site: 00105 distlib.metadata.LegacyMetadata.update
6 153 distlib.metadata.Metadata._validate_mapping call site: 00153 distlib.metadata.LegacyMetadata.__init__
5 141 distlib.metadata._best_version call site: 00141 distlib.metadata.LegacyMetadata.read_file
3 2 ...fuzz_metadata.TestOneInput call site: 00002 distlib.metadata.LegacyMetadata.read
3 168 distlib.metadata.LegacyMetadata.get call site: 00168 res.append
3 173 distlib.metadata.Metadata.validate call site: 00173 distlib.metadata.Metadata._validate_mapping
2 17 distlib.metadata.LegacyMetadata.set call site: 00017 .isinstance
2 79 distlib.version.Version.__init__ call site: 00079 distlib.version.Version.__init__
2 127 distlib.metadata._best_version call site: 00127 possible_versions.remove
1 13 distlib.metadata.LegacyMetadata._convert_name call site: 00013 .isinstance

Runtime coverage analysis

Covered functions
98
Functions that are reachable but not covered
71
Reachable functions
94
Percentage of reachable functions covered
24.47%
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_metadata 8
distlib.metadata 59
distlib.version 35

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
distlib.wheel.Wheel.install distlib.wheel 4 ['N/A', 'N/A', 'N/A', 'N/A'] 10 0 21 25 13 207 0 691 381
distlib.scripts.ScriptMaker._copy_script distlib.scripts 3 ['N/A', 'N/A', 'N/A'] 5 0 10 10 7 83 2 279 211
distlib.locators.SimpleScrapingLocator._fetch distlib.locators 1 ['N/A'] 13 0 6 5 5 155 0 526 192
distlib.database.DistributionPath.provides_distribution distlib.database 3 ['N/A', 'N/A', 'N/A'] 16 0 4 5 5 161 0 556 135
distlib.wheel.Wheel.update distlib.wheel 4 ['N/A', 'N/A', 'N/A', 'N/A'] 11 0 7 8 6 147 0 501 120
distlib.index.PackageIndex.upload_file distlib.index 8 ['N/A', 'N/A', 'N/A', 'N/A', 'N/A', 'N/A', 'N/A', 'N/A'] 3 0 7 4 5 51 0 161 107
distlib.wheel.Wheel.mount distlib.wheel 2 ['N/A', 'N/A'] 4 0 5 6 5 43 0 140 81
distlib.manifest.Manifest.process_directive distlib.manifest 2 ['N/A', 'N/A'] 4 0 6 13 8 33 0 118 77
distlib.locators.Locator.locate distlib.locators 3 ['N/A', 'N/A', 'N/A'] 12 0 5 10 7 88 0 300 65
distlib.locators.DependencyFinder.find distlib.locators 4 ['N/A', 'N/A', 'N/A', 'N/A'] 7 0 17 15 9 57 0 194 59

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

Functions statically reachable by fuzzers
30.0%
174 / 575
Cyclomatic complexity statically reachable by fuzzers
35.0%
728 / 2097

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

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
distlib.version._suggest_normalized_version 33 2 6.060% []
distlib.util.unarchive.check_path 36 0 0.0% []
distlib.util.get_host_platform 41 1 2.439% []
distlib.metadata.Metadata.__getattribute__ 34 6 17.64% []
distlib.metadata.Metadata._to_legacy.process_entries 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
[] []
urlparse [] []
platform [] []
sysconfig [] []
dummy_thread [] []
distlib.markers ['fuzz_marker'] []
html [] []
httplib [] []
ConfigParser [] []
datetime [] []
ssl [] []
imp [] []
re [] []
base64 [] []
distlib.index [] []
pkgutil [] []
struct [] []
distlib.wheel [] []
distlib.manifest [] []
textwrap [] []
distlib.resources [] []
json [] []
subprocess [] []
sys [] []
contextlib [] []
_aix_support [] []
fnmatch [] []
threading [] []
queue [] []
email [] []
codecs [] []
distlib.version ['fuzz_marker', 'fuzz_metadata'] []
bisect [] []
tempfile [] []
csv [] []
time [] []
distlib.metadata ['fuzz_metadata'] []
types [] []
distlib.compat [] []
...fuzz_marker ['fuzz_marker'] []
distlib.database [] []
StringIO [] []
hashlib [] []
itertools [] []
os [] []
posixpath [] []
py_compile [] []
http [] []
shutil [] []
tarfile [] []
distutils [] []
_abcoll [] []
glob [] []
zipfile [] []
zipimport [] []
dummy_threading [] []
thread [] []
warnings [] []
distlib.scripts [] []
urllib2 [] []
socket [] []
...fuzz_metadata ['fuzz_metadata'] []
HTMLParser [] []
distlib.locators [] []
configparser [] []
distlib [] []
stat [] []
atheris [] []
reprlib [] []
xmlrpc [] []
_osx_support [] []
xmlrpclib [] []
logging [] []
importlib [] []
java [] []
[] []
io [] []
collections [] []
tokenize [] []
urllib [] []
distlib.util ['fuzz_marker'] []

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_marker fuzzerLogFile-fuzz_marker.data fuzzerLogFile-fuzz_marker.data.yaml all_cov.json
fuzz_metadata fuzzerLogFile-fuzz_metadata.data fuzzerLogFile-fuzz_metadata.data.yaml all_cov.json