Report generation date: 2025-06-29

Project overview: tinygltf

High level conclusions

Fuzzers reach 48.22% of cyclomatic complexity.

"No files with coverage data was found. This is either because an error occurred when compiling and running coverage runs, or because the introspector run was intentionally done without coverage collection. In order to get optimal results coverage data is needed.

Reachability and coverage overview

Functions statically reachable by fuzzers

501 / 1040

Cyclomatic complexity statically reachable by fuzzers

6686 / 13865

Runtime code coverage of functions

0 / 1040

Fuzzers overview

Fuzzer	Fuzzer filename	Functions Reached	Functions unreached	Fuzzer depth	Files reached	Basic blocks reached	Cyclomatic complexity	Details
fuzz_gltf	/src/tinygltf/tests/fuzzer/build/../fuzz_gltf.cc	994	580	24	4	14282	6778	fuzz_gltf.cc

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_gltf

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 project has no code coverage. Will not display blockers as blockers depend on code coverage.

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	total cyclomatic complexity	Unreached complexity
`tinygltf::LoadImageData(tinygltf::Image,int,std::__1::basic_string ,std::__1::allocator >,std::__1::basic_string ,std::__1::allocator >,int,int,unsignedcharconst,int,void*)`	/src/tinygltf/tests/fuzzer/build/../../../tiny_gltf.h	9	['N/A', 'int', 'N/A', 'N/A', 'int', 'int', 'N/A', 'int', 'N/A']	15	1752	185	14	339	3078	3029
`tinygltf::TinyGLTF::WriteGltfSceneToFile(tinygltf::Modelconst*,std::__1::basic_string ,std::__1::allocator >const&,bool,bool,bool,bool)`	/src/tinygltf/tests/fuzzer/build/../../../tiny_gltf.h	7	['N/A', 'N/A', 'N/A', 'bool', 'bool', 'bool', 'bool']	19	1525	177	163	540	2954	1951
`tinygltf::WriteImageData(std::__1::basic_string ,std::__1::allocator >const,std::__1::basic_string ,std::__1::allocator >const,tinygltf::Imageconst,bool,tinygltf::FsCallbacksconst,tinygltf::URICallbacksconst,std::__1::basic_string ,std::__1::allocator >,void*)`	/src/tinygltf/tests/fuzzer/build/../../../tiny_gltf.h	8	['N/A', 'N/A', 'N/A', 'bool', 'N/A', 'N/A', 'N/A', 'N/A']	8	944	148	26	83	642	568
`stbi_write_hdr`	/src/tinygltf/tests/fuzzer/build/../../../stb_image_write.h	5	['N/A', 'int', 'int', 'int', 'N/A']	4	146	13	6	38	145	109
`tinygltf::GetFileSizeInBytes(unsignedlong,std::__1::basic_string ,std::__1::allocator >,std::__1::basic_string ,std::__1::allocator >const&,void*)`	/src/tinygltf/tests/fuzzer/build/../../../tiny_gltf.h	4	['N/A', 'N/A', 'N/A', 'N/A']	1	818	103	93	5	103	93
`tinygltf::ReadWholeFile(std::__1::vector >,std::__1::basic_string ,std::__1::allocator >,std::__1::basic_string ,std::__1::allocator >const&,void*)`	/src/tinygltf/tests/fuzzer/build/../../../tiny_gltf.h	4	['N/A', 'N/A', 'N/A', 'N/A']	1	825	105	91	4	99	91
`tinygltf::TinyGLTF::LoadBinaryFromFile(tinygltf::Model,std::__1::basic_string ,std::__1::allocator >,std::__1::basic_string ,std::__1::allocator >*,std::__1::basic_string ,std::__1::allocator >const&,unsignedint)`	/src/tinygltf/tests/fuzzer/build/../../../tiny_gltf.h	6	['N/A', 'N/A', 'N/A', 'N/A', 'N/A', 'int']	21	506	52	46	987	6797	90
`tinygltf::TinyGLTF::WriteGltfSceneToStream(tinygltf::Modelconst*,std::__1::basic_ostream >&,bool,bool)`	/src/tinygltf/tests/fuzzer/build/../../../tiny_gltf.h	5	['N/A', 'N/A', 'N/A', 'bool', 'bool']	19	669	81	79	526	2838	79
`tinygltf::Material::operator==(tinygltf::Materialconst&)const`	/src/tinygltf/tests/fuzzer/build/../../../tiny_gltf.h	2	['N/A', 'N/A']	6	190	38	16	58	133	71
`stbi__idct_block(unsignedchar,int,short)`	/src/tinygltf/tests/fuzzer/build/../../../stb_image.h	3	['N/A', 'int', 'N/A']	1	1519	178	62	8	78	66

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

Functions statically reachable by fuzzers

860 / 1040

Cyclomatic complexity statically reachable by fuzzers

12811 / 13865

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/tinygltf/tests/fuzzer/build/../fuzz_gltf.cc

Dictionary

Use this with the libFuzzer -dict=DICT.file flag

Runtime coverage analysis

No runtime coverage data was found

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
	[]	[]
/usr/local/bin/../include/c++/v1/stdexcept	[]	[]
/src/tinygltf/tests/fuzzer/build/../../../stb_image.h	[]	[]
/usr/local/bin/../include/c++/v1/initializer_list	[]	[]
/src/tinygltf/tests/fuzzer/build/../../../json.hpp	['fuzz_gltf']	[]
/src/tinygltf/tests/fuzzer/build/../../../tiny_gltf.h	['fuzz_gltf']	[]
/usr/local/bin/../include/c++/v1/sstream	[]	[]
/src/tinygltf/tests/fuzzer/build/../../../stb_image_write.h	[]	[]
/usr/local/bin/../include/c++/v1/string	[]	[]
/src/tinygltf/tests/fuzzer/build/../fuzz_gltf.cc	['fuzz_gltf']	[]
/usr/local/bin/../include/c++/v1/__exception/exception.h	['fuzz_gltf']	[]

Directories in report

Directory

/usr/local/bin/../include/c++/v1/__exception/
/usr/local/bin/../include/c++/v1/
/src/tinygltf/tests/fuzzer/build/../../../
/src/tinygltf/tests/fuzzer/build/../

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_gltf fuzzerLogFile-0-lTe2ggILf1.data fuzzerLogFile-0-lTe2ggILf1.data.yaml

Table of contents