Fuzz introspector
For issues and ideas: https://github.com/ossf/fuzz-introspector/issues
Report generation date: 2025-06-22

Project overview: numpy

High level conclusions

Reachability and coverage overview

Functions statically reachable by fuzzers
0.0%
1 / 3548
Cyclomatic complexity statically reachable by fuzzers
0.0%
3 / 13058
Runtime code coverage of functions
0.0%
7 / 3548

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.

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_fromfile_loader

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 6 100.%
gold [1:9] 0 0.0%
yellow [10:29] 0 0.0%
greenyellow [30:49] 0 0.0%
lawngreen 50+ 0 0.0%
All colors 6 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
5 0 EP call site: 00000 tempfile.NamedTemporaryFile

Runtime coverage analysis

Covered functions
19
Functions that are reachable but not covered
6
Reachable functions
6
Percentage of reachable functions covered
0.0%
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_fromfile_loader 5

Fuzzer: fuzz_datetime

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

Runtime coverage analysis

Covered functions
19
Functions that are reachable but not covered
3
Reachable functions
3
Percentage of reachable functions covered
0.0%
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_datetime 2

Fuzzer: fuzz_binary_loader

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 7 100.%
gold [1:9] 0 0.0%
yellow [10:29] 0 0.0%
greenyellow [30:49] 0 0.0%
lawngreen 50+ 0 0.0%
All colors 7 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
6 0 EP call site: 00000 tempfile.NamedTemporaryFile

Runtime coverage analysis

Covered functions
19
Functions that are reachable but not covered
7
Reachable functions
7
Percentage of reachable functions covered
0.0%
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_binary_loader 6

Fuzzer: fuzz_dtype

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

Runtime coverage analysis

Covered functions
19
Functions that are reachable but not covered
3
Reachable functions
3
Percentage of reachable functions covered
0.0%
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_dtype 2

Fuzzer: fuzz_fromregex_loader

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

Runtime coverage analysis

Covered functions
19
Functions that are reachable but not covered
10
Reachable functions
10
Percentage of reachable functions covered
0.0%
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_fromregex_loader 9

Fuzzer: fuzz_loader

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 6 100.%
gold [1:9] 0 0.0%
yellow [10:29] 0 0.0%
greenyellow [30:49] 0 0.0%
lawngreen 50+ 0 0.0%
All colors 6 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
5 0 EP call site: 00000 ...fuzz_loader.get_fuzz_types

Runtime coverage analysis

Covered functions
19
Functions that are reachable but not covered
6
Reachable functions
6
Percentage of reachable functions covered
0.0%
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_loader 5

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
[] []
numpy.lib._nanfunctions_impl [] []
numpy._typing._nested_sequence [] []
contextvars [] []
...fuzz_fromregex_loader ['fuzz_fromregex_loader'] []
numpy.distutils.command.config_compiler [] []
numpy.f2py.cfuncs [] []
numpy.lib.user_array [] []
numpy.lib._npyio_impl [] []
numpy._core.numerictypes [] []
numpy.lib.format [] []
numpy.distutils.command.build_src [] []
numpy.f2py.crackfortran [] []
numpy._core._asarray [] []
threading [] []
scipy_doctest [] []
numpy.distutils.command.install_headers [] []
numpy.lib._histograms_impl [] []
numpy._typing._nbit [] []
numpy.lib.npyio [] []
gc [] []
numpy.distutils.fcompiler.fujitsu [] []
inspect [] []
numpy.distutils.fcompiler.hpux [] []
numpy._expired_attrs_2_0 [] []
pprint [] []
numpy._array_api_info [] []
numpy.f2py._backends._meson [] []
numpy.distutils.cpuinfo [] []
numpy.distutils.unixccompiler [] []
numpy.core.arrayprint [] []
numpy.distutils.ccompiler_opt [] []
numpy.lib.introspect [] []
numpy.polynomial._polybase [] []
numpy._typing._ufunc [] []
doctest [] []
distutils [] []
copyreg [] []
pydoc [] []
numpy._core.memmap [] []
...fuzz_datetime ['fuzz_datetime'] []
numpy.ma.testutils [] []
numpy.testing.print_coercion_tables [] []
numpy.linalg._linalg [] []
numpy.distutils.fcompiler.none [] []
numpy.distutils.fcompiler.intel [] []
numpy._core._ufunc_config [] []
numpy._configtool [] []
numpy.core.multiarray [] []
numpy.f2py.rules [] []
numpy.matrixlib [] []
numpy.f2py.cb_rules [] []
time [] []
numpy.fft._helper [] []
numpy.f2py.symbolic [] []
base64 [] []
numpy._core._internal [] []
numpy._utils._inspect [] []
numpy.core._multiarray_umath [] []
numpy._core.printoptions [] []
numpy.exceptions [] []
numpy.f2py.capi_maps [] []
numpy.distutils.lib2def [] []
numpy.ma.core [] []
numpy.distutils.from_template [] []
numpy.matlib [] []
numpy._typing._dtype_like [] []
numpy.random._examples.numba.extending [] []
argparse [] []
numpy.testing._private [] []
numpy.testing [] []
numpy.distutils.command.bdist_rpm [] []
numpy.core.shape_base [] []
...fuzz_binary_loader ['fuzz_binary_loader'] []
numpy.core._internal [] []
numpy.core.numeric [] []
json [] []
winreg [] []
numpy._typing._nbit_base [] []
traceback [] []
numpy._utils._convertions [] []
numpy._core.function_base [] []
numpy.polynomial.polyutils [] []
numpy.random._examples.cffi.extending [] []
numpy.core.einsumfunc [] []
subprocess [] []
numpy.lib._utils_impl [] []
functools [] []
numpy.core._dtype_ctypes [] []
numpy.distutils [] []
...fuzz_fromfile_loader ['fuzz_fromfile_loader'] []
numpy.testing._private.utils [] []
numpy.lib.scimath [] []
atexit [] []
numpy.lib._shape_base_impl [] []
fileinput [] []
tokenize [] []
zipfile [] []
numpy.core.defchararray [] []
numpy.polynomial.hermite [] []
numpy.polynomial.laguerre [] []
numpy.lib._twodim_base_impl [] []
numpy.distutils.command.autodist [] []
unittest [] []
numpy._core.fromnumeric [] []
numpy.distutils.core [] []
numpy.distutils.command.install [] []
numpy.f2py.common_rules [] []
numpy.fft._pocketfft [] []
numpy.ctypeslib [] []
numpy.core.function_base [] []
_pcg64 [] []
numpy._core [] []
numpy.core._utils [] []
atheris [] []
numpy._core._methods [] []
numpy.core.getlimits [] []
numpy.distutils.command.egg_info [] []
numpy.lib.mixins [] []
builtins [] []
numpy.polynomial.legendre [] []
numpy._utils._pep440 [] []
...fuzz_loader ['fuzz_loader'] []
numpy.distutils.numpy_distribution [] []
numpy.random._examples.cffi.parse [] []
numpy.f2py._backends._distutils [] []
string [] []
numpy.f2py.func2subr [] []
numpy.core.overrides [] []
typing [] []
timeit [] []
mypy [] []
numpy.core.records [] []
numpy.random [] []
numpy.distutils.command.develop [] []
contextlib [] []
numpy.distutils.fcompiler.absoft [] []
numpy.lib._user_array_impl [] []
numpy.random._pickle [] []
numpy.rec [] []
numpy._core.umath [] []
difflib [] []
numpy._pyinstaller [] []
numpy.distutils.pathccompiler [] []
numpy.lib._function_base_impl [] []
numpy.distutils.conv_template [] []
concurrent [] []
charset_normalizer [] []
numpy.distutils.command.sdist [] []
ctypes [] []
numpy.f2py.__main__ [] []
_pocketfft_umath [] []
numpy.distutils.command.config [] []
numpy.distutils.extension [] []
numpy._typing [] []
win32pdh [] []
_multiarray_umath [] []
numpy.core.umath [] []
numpy.distutils.fcompiler.arm [] []
numpy.distutils.command [] []
numpy.distutils.command.build_ext [] []
weakref [] []
numpy._core.defchararray [] []
numpy._core._machar [] []
numpy.lib._polynomial_impl [] []
collections [] []
numpy.f2py.f2py2e [] []
numpy._core._dtype_ctypes [] []
mtrand [] []
numpy.distutils.command.build_scripts [] []
sysconfig [] []
numpy.polynomial.hermite_e [] []
optparse [] []
pytest [] []
numpy.dtypes [] []
math [] []
numpy._core._string_helpers [] []
numpy.polynomial [] []
abc [] []
hypothesis [] []
numpy._core.arrayprint [] []
psutil [] []
numpy._core.shape_base [] []
numpy.core [] []
shlex [] []
numpy.distutils.intelccompiler [] []
cffi [] []
numpy.lib._arrayterator_impl [] []
numpy.distutils.msvc9compiler [] []
numpy.distutils.fcompiler.environment [] []
numpy.distutils.line_endings [] []
numpy.distutils.fujitsuccompiler [] []
[] []
numpy.distutils.command.build [] []
numpy.conftest [] []
numpy.distutils.fcompiler.lahey [] []
numpy._core._type_aliases [] []
numpy [] []
numpy.distutils.fcompiler.g95 [] []
numpy._typing._char_codes [] []
yaml [] []
numpy.lib._type_check_impl [] []
numpy.distutils.exec_command [] []
platform [] []
numpy.lib [] []
numpy._core.tests._natype [] []
code_generators [] []
numpy.lib._ufunclike_impl [] []
numpy._core._dtype [] []
...fuzz_dtype ['fuzz_dtype'] []
numpy.distutils.fcompiler.pathf95 [] []
numpy.distutils.fcompiler.mips [] []
numpy.f2py.use_rules [] []
types [] []
numpy.distutils.misc_util [] []
threadpoolctl [] []
numpy._pyinstaller.hook-numpy [] []
numpy.lib.recfunctions [] []
numpy.core.fromnumeric [] []
numpy.distutils.armccompiler [] []
numpy._utils [] []
_mt19937 [] []
numpy.distutils.ccompiler [] []
numpy.distutils.msvccompiler [] []
sys [] []
numpy._pytesttester [] []
numpy.distutils.system_info [] []
numpy.typing.mypy_plugin [] []
glob [] []
numpy.distutils.fcompiler.gnu [] []
numbers [] []
ast [] []
numpy.lib._arraysetops_impl [] []
numpy._typing._array_like [] []
numpy.distutils.fcompiler [] []
numpy._core._add_newdocs_scalars [] []
numpy.fft.helper [] []
copy [] []
numpy.lib._scimath_impl [] []
numpy.f2py.diagnose [] []
numpy._distributor_init [] []
numpy.fft [] []
struct [] []
numpy.testing.overrides [] []
configparser [] []
numpy.distutils.fcompiler.nag [] []
numpy.doc.ufuncs [] []
numpy.lib._array_utils_impl [] []
numpy.matrixlib.defmatrix [] []
numpy.ma.extras [] []
numpy.linalg [] []
numpy._core.cversions [] []
locale [] []
numpy.distutils.command.build_py [] []
numpy.ctypeslib._ctypeslib [] []
numpy.distutils.command.install_clib [] []
numpy.f2py.f90mod_rules [] []
numpy.distutils.fcompiler.nv [] []
curses [] []
shutil [] []
_generator [] []
numpy._core.strings [] []
numpy._core._exceptions [] []
numba [] []
numpy._core.multiarray [] []
textwrap [] []
numpy.ma.mrecords [] []
numpy.distutils.npy_pkg_config [] []
numpy._core.numeric [] []
numpy.f2py._isocbind [] []
_dummy_thread [] []
numpy.distutils.log [] []
numpy.distutils.command.build_clib [] []
os [] []
numpy.distutils._shell_utils [] []
pathlib [] []
numpy._typing._scalars [] []
numpy.strings [] []
numpy._typing._shape [] []
numpy.lib._stride_tricks_impl [] []
numpy.distutils.fcompiler.ibm [] []
numpy._core.overrides [] []
numpy._globals [] []
re [] []
numpy.__config__ [] []
numpy._core.einsumfunc [] []
numpy.typing [] []
numpy._core.getlimits [] []
numpy.distutils.fcompiler.sun [] []
numpy.core.numerictypes [] []
setuptools [] []
numpy.linalg.linalg [] []
numpy.lib._arraypad_impl [] []
numpy.f2py._backends._backend [] []
itertools [] []
numpy.f2py._src_pyf [] []
urllib [] []
numpy.distutils.fcompiler.vast [] []
numpy.lib._iotools [] []
numpy._core.records [] []
numpy._core._add_newdocs [] []
multiprocessing [] []
PyInstaller [] []
numpy.char [] []
numpy._typing._add_docstring [] []
numpy.lib.stride_tricks [] []
numpy.core._dtype [] []
numpy.lib._format_impl [] []
numpy.lib._index_tricks_impl [] []
numpy.distutils.fcompiler.compaq [] []
numpy.lib._datasource [] []
mmap [] []
numpy.testing._private.extbuild [] []
numpy.lib._version [] []
numpy.ma [] []
numpy.distutils.mingw32ccompiler [] []
numpy.distutils.fcompiler.pg [] []
numpy.f2py.__version__ [] []
numpy.random._examples.numba.extending_distributions [] []
numpy._typing._extended_precision [] []
numpy.polynomial.chebyshev [] []
numpy.polynomial.polynomial [] []
warnings [] []
numpy.distutils.command.install_data [] []
_thread [] []
numpy.f2py [] []
numpy_distutils [] []
pickle [] []
numpy.f2py.auxfuncs [] []
tempfile [] []
numpy.version [] []
hashlib [] []
io [] []
numpy.lib.array_utils [] []
operator [] []
numpy.f2py._backends [] []

Directories in report

Directory