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

Table of contents

Project overview: pydantic
High level conclusions
Reachability and coverage overview
Fuzzers overview
Project functions overview
Fuzzer details
Fuzzer: fuzz_date
Call tree
Runtime coverage analysis
Files reached
Fuzzer: fuzz_network
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-04-27

Project overview: pydantic

High level conclusions

Reachability and coverage overview

Functions statically reachable by fuzzers
0.0%
1 / 740
Cyclomatic complexity statically reachable by fuzzers
0.0%
3 / 2572
Runtime code coverage of functions
85.0%
628 / 740

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_date /src/fuzz_date.py 1022 60426 2 3 0 3063 fuzz_date.py
fuzz_network /src/fuzz_network.py 848 58281 2 3 0 2541 fuzz_network.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_date

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

Runtime coverage analysis

Covered functions
245
Functions that are reachable but not covered
1021
Reachable functions
1022
Percentage of reachable functions covered
0.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.
Function name source code lines source lines hit percentage hit

Files reached

filename functions hit
/ 1
...fuzz_date 3
pydantic.main 1018

Fuzzer: fuzz_network

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 1 0.11%
gold [1:9] 0 0.0%
yellow [10:29] 0 0.0%
greenyellow [30:49] 0 0.0%
lawngreen 50+ 847 99.8%
All colors 848 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
1 0 EP call site: 00000 atheris.FuzzedDataProvider

Runtime coverage analysis

Covered functions
245
Functions that are reachable but not covered
847
Reachable functions
848
Percentage of reachable functions covered
0.12%
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.
Function name source code lines source lines hit percentage hit

Files reached

filename functions hit
/ 1
...fuzz_network 3
pydantic.main 844

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
pydantic.deprecated.tools.schema_of pydantic.deprecated.tools 5 ['N/A', 'N/A', 'N/A', 'N/A', 'N/A'] 28 0 3 2 4 29921 1 89887 86830

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

Functions statically reachable by fuzzers
19.0%
137 / 740
Cyclomatic complexity statically reachable by fuzzers
21.0%
530 / 2572

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
pydantic.main.BaseModel.__class_getitem__ 36 0 0.0% []
pydantic.main.create_model 36 0 0.0% []
pydantic._internal._generate_schema.GenerateSchema._generate_schema 122 27 22.13% []
pydantic._internal._generate_schema.apply_single_annotation 33 0 0.0% []
typing_extensions.TypedDict.__bound__.model_config.__supertype__.pop 900 375 41.66% []
pydantic._internal._model_construction.inspect_namespace 37 15 40.54% []
pydantic._internal._decorators.DecoratorInfos.build 36 14 38.88% []
pydantic._internal._generics.replace_types 36 0 0.0% []
pydantic.fields.FieldInfo.from_annotated_attribute 39 0 0.0% []
pydantic.fields.Field 34 3 8.823% []
pydantic._internal._fields.collect_model_fields 43 22 51.16% []
pydantic._internal._validators.DecimalValidator.__call__ 42 0 0.0% []
pydantic._internal._discriminated_union._ApplyInferredDiscriminator._infer_discriminator_values_for_choice 33 0 0.0% []
typing_extensions.TypedDict.type.model_config.__bound__.__supertype__.__init__.pop 900 375 41.66% []

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
[] []
functools [] []
uuid [] []
pydantic.tools [] []
pydantic.deprecated.tools [] []
pydantic.version [] []
mypy [] []
pydantic.class_validators [] []
annotated_types [] []
pydantic.env_settings [] []
pydantic._internal._dataclasses [] []
pydantic._internal._utils [] []
pydantic.main ['fuzz_date', 'fuzz_network'] []
pydantic._internal._repr [] []
pickle [] []
pydantic._internal._generics [] []
pydantic._internal._core_utils [] []
pydantic.json [] []
pydantic._internal._json_schema_shared [] []
contextlib [] []
tomli [] []
hypothesis [] []
pydantic._internal._core_metadata [] []
types [] []
pydantic._internal._decorators [] []
pydantic.analyzed_type [] []
pydantic.dataclasses [] []
warnings [] []
pydantic.deprecated.decorator [] []
pydantic._migration [] []
pydantic.types [] []
pydantic._internal._generate_schema [] []
pydantic.deprecated.config [] []
pydantic.mypy [] []
pydantic._internal._fields [] []
pydantic._internal._model_construction [] []
datetime [] []
pydantic._internal._decorators_v1 [] []
typing [] []
pydantic.validators [] []
fractions [] []
weakref [] []
pydantic._hypothesis_plugin [] []
json [] []
pydantic.deprecated [] []
pydantic._internal._discriminated_union [] []
itertools [] []
atheris [] []
pydantic.annotated_arguments [] []
sys [] []
math [] []
dataclasses [] []
pydantic._internal._validators [] []
contextvars [] []
pydantic.deprecated.copy_internals [] []
tomllib [] []
decimal [] []
pydantic [] []
pydantic.fields [] []
pydantic._internal [] []
importlib [] []
re [] []
pydantic._internal._serializers [] []
pydantic.errors [] []
pydantic.schema [] []
abc [] []
pydantic._internal._config [] []
...fuzz_network ['fuzz_network'] []
pydantic._internal._validate_call [] []
ipaddress [] []
pydantic.config [] []
pydantic.decorators [] []
pydantic.deprecated.json [] []
pydantic.deprecated.parse [] []
pydantic_core [] []
pydantic._internal._forward_ref [] []
pydantic.typing [] []
pydantic._internal._std_types_schema [] []
[] []
pydantic.networks [] []
email_validator [] []
pydantic.json_schema [] []
pydantic.validate_call [] []
copy [] []
colorsys [] []
typing_extensions [] []
pydantic.generics [] []
pydantic.error_wrappers [] []
keyword [] []
pathlib [] []
pydantic.color [] []
pydantic.utils [] []
pydantic.decorator [] []
pydantic._internal._internal_dataclass [] []
inspect [] []
pydantic._internal._typing_extra [] []
...fuzz_date ['fuzz_date'] []
pydantic.parse [] []
configparser [] []
collections [] []

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_date fuzzerLogFile-fuzz_date.data fuzzerLogFile-fuzz_date.data.yaml all_cov.json
fuzz_network fuzzerLogFile-fuzz_network.data fuzzerLogFile-fuzz_network.data.yaml all_cov.json