High level conclusions

Fuzzer fuzz_payload_url is blocked:

The runtime code coverage of fuzz_payload_url covers 27.50% of its statically reachable code. This means there is some place that blocks the fuzzer to continue exploring more code at run time.

Fuzzer fuzz_multipart is blocked:

The runtime code coverage of fuzz_multipart covers 0.0% of its statically reachable code. This means there is some place that blocks the fuzzer to continue exploring more code at run time.

Fuzzer fuzz_web_request is blocked:

The runtime code coverage of fuzz_web_request covers 23.65% of its statically reachable code. This means there is some place that blocks the fuzzer to continue exploring more code at run time.

Fuzzer fuzz_http_parser_pure_python is blocked:

The runtime code coverage of fuzz_http_parser_pure_python covers 20.0% of its statically reachable code. This means there is some place that blocks the fuzzer to continue exploring more code at run time.

Fuzzer fuzz_http_payload_parser is blocked:

The runtime code coverage of fuzz_http_payload_parser covers 29.41% of its statically reachable code. This means there is some place that blocks the fuzzer to continue exploring more code at run time.

Fuzzer fuzz_http_payload_parser_pure_python is blocked:

The runtime code coverage of fuzz_http_payload_parser_pure_python covers 29.41% of its statically reachable code. This means there is some place that blocks the fuzzer to continue exploring more code at run time.

Fuzzer fuzz_http_parser is blocked:

The runtime code coverage of fuzz_http_parser covers 20.0% of its statically reachable code. This means there is some place that blocks the fuzzer to continue exploring more code at run time.

Reachability and coverage overview

Functions statically reachable by fuzzers

57 / 1390

Cyclomatic complexity statically reachable by fuzzers

219 / 4736

Runtime code coverage of functions

241 / 1390

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.

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: fuzz_http_parser

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

Runtime coverage analysis

Covered functions

248

Functions that are reachable but not covered

4

Reachable functions

5

Percentage of reachable functions covered

20.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
...aiohttp.fuzz_http_parser	4

Fuzzer: fuzz_http_payload_parser_pure_python

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	31	42.4%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	42	57.5%
All colors	73	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
24	0	EP	call site: 00000	aiohttp.http_parser.HttpPayloadParser.feed_data
4	43	aiohttp.http_parser.HttpPayloadParser.feed_data	call site: 00043	aiohttp.streams.StreamReader.set_exception
1	28	aiohttp.streams.StreamReader.feed_data	call site: 00028	aiohttp.helpers.set_result
1	38	aiohttp.http_parser.HttpPayloadParser.feed_data	call site: 00038	size_b.strip
1	60	aiohttp.http_parser.HttpPayloadParser.feed_data	call site: 00060	aiohttp.helpers.set_result

Runtime coverage analysis

Covered functions

248

Functions that are reachable but not covered

24

Reachable functions

34

Percentage of reachable functions covered

29.41%

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
...aiohttp.fuzz_http_payload_parser_pure_python	4
aiohttp.http_parser	20
aiohttp.compression_utils	5
aiohttp.streams	5
aiohttp.helpers	2
aiohttp.http_exceptions	1

Fuzzer: fuzz_http_payload_parser

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	31	42.4%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	42	57.5%
All colors	73	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
24	0	EP	call site: 00000	aiohttp.http_parser.HttpPayloadParser.feed_data
4	43	aiohttp.http_parser.HttpPayloadParser.feed_data	call site: 00043	aiohttp.streams.StreamReader.set_exception
1	28	aiohttp.streams.StreamReader.feed_data	call site: 00028	aiohttp.helpers.set_result
1	38	aiohttp.http_parser.HttpPayloadParser.feed_data	call site: 00038	size_b.strip
1	60	aiohttp.http_parser.HttpPayloadParser.feed_data	call site: 00060	aiohttp.helpers.set_result

Runtime coverage analysis

Covered functions

248

Functions that are reachable but not covered

24

Reachable functions

34

Percentage of reachable functions covered

29.41%

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
...aiohttp.fuzz_http_payload_parser	4
aiohttp.http_parser	20
aiohttp.compression_utils	5
aiohttp.streams	5
aiohttp.helpers	2
aiohttp.http_exceptions	1

Fuzzer: fuzz_http_parser_pure_python

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

Runtime coverage analysis

Covered functions

248

Functions that are reachable but not covered

4

Reachable functions

5

Percentage of reachable functions covered

20.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
...aiohttp.fuzz_http_parser_pure_python	4

Fuzzer: fuzz_web_request

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	92	56.7%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	70	43.2%
All colors	162	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
59	102	multidict._multidict_py.MultiDictProxy.__init__	call site: 00102	aiohttp.web_request.BaseRequest.multipart
8	39	multidict._multidict_py.MultiDict._extend	call site: 00039	aiohttp.test_utils.make_mocked_request
6	0	EP	call site: 00000	...aiohttp.fuzz_web_request.fuzz_run_one_async
6	25	multidict._multidict_py.MultiDict._extend	call site: 00025	used_keys.get
4	13	multidict._multidict_py.MultiDict._extend	call site: 00013	.list
4	56	aiohttp.test_utils.make_mocked_request	call site: 00056	multidict._multidict_py._Base.items
4	61	multidict._multidict_py._Base.items	call site: 00061	multidict._multidict_py.MultiDict.__init__
1	92	aiohttp.web_urldispatcher.UrlMappingMatchInfo.__init__	call site: 00092	unittest.mock.Mock

Runtime coverage analysis

Covered functions

311

Functions that are reachable but not covered

71

Reachable functions

93

Percentage of reachable functions covered

23.66%

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
...aiohttp.fuzz_web_request	10
multidict._multidict_py	24
aiohttp.test_utils	23
aiohttp.web_request	31
aiohttp.web_urldispatcher	2
aiohttp.multipart	3
aiohttp.helpers	11

Fuzzer: fuzz_multipart

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	78	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	78	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
77	0	EP	call site: 00000	...aiohttp.fuzz_multipart.fuzz_bodypart_reader

Runtime coverage analysis

Covered functions

248

Functions that are reachable but not covered

57

Reachable functions

57

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
...aiohttp.fuzz_multipart	8
aiohttp.multipart	29
aiohttp.compression_utils	3
aiohttp.helpers	9
aiohttp.client_reqrep	10

Fuzzer: fuzz_payload_url

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	36	58.0%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	26	41.9%
All colors	62	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	45	multidict._multidict_py.MultiDictProxy.__init__	call site: 00045	multidict._multidict_py.MultiDict.__init__
6	24	multidict._multidict_py.MultiDict._extend	call site: 00024	used_keys.get
6	38	multidict._multidict_py.MultiDict._extend	call site: 00038	multidict._multidict_py.CIMultiDict._title
5	0	EP	call site: 00000	aiohttp.payload.StringPayload.__init__
4	12	multidict._multidict_py.MultiDict._extend	call site: 00012	.list
2	59	aiohttp.payload.StringPayload.__init__	call site: 00059	urllib.parse.urlencode.encode

Runtime coverage analysis

Covered functions

311

Functions that are reachable but not covered

29

Reachable functions

40

Percentage of reachable functions covered

27.5%

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
...aiohttp.fuzz_payload_url	3
aiohttp.payload	5
aiohttp.helpers	11
multidict._multidict_py	20

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
aiohttp.client.ClientSession._ws_connect	aiohttp.client	20	['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', 'N/A', 'N/A', 'N/A', 'N/A', 'N/A', 'N/A', 'N/A']	6	0	5	16	9	233	1	792	709
aiohttp.connector.BaseConnector.connect	aiohttp.connector	4	['N/A', 'N/A', 'N/A', 'N/A']	7	0	23	12	8	198	0	663	275
aiohttp.web.main	aiohttp.web	1	['N/A']	6	0	12	3	4	94	1	295	259
aiohttp.web_protocol.RequestHandler.start	aiohttp.web_protocol	1	['N/A']	7	0	16	14	9	99	1	338	247
yarl._url.URL.__new__	yarl._url	4	['N/A', 'N/A', 'N/A', 'N/A']	3	0	2	10	7	34	0	114	96
aiohttp.web_urldispatcher.UrlDispatcher.add_resource	aiohttp.web_urldispatcher	3	['N/A', 'N/A', 'N/A']	4	0	2	4	5	29	9	95	77
aiohttp.multipart.parse_content_disposition	aiohttp.multipart	1	['N/A']	2	0	9	15	9	22	3	75	63

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

Functions statically reachable by fuzzers

219 / 1390

Cyclomatic complexity statically reachable by fuzzers

885 / 4736

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

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/aiohttp/fuzz_http_parser.py

Dictionary

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

/src/aiohttp/fuzz_http_payload_parser_pure_python.py

Dictionary

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

Fuzzer function priority

Use one of these functions as input to libfuzzer with flag: -focus_function name

-focus_function=['aiohttp.http_parser.HttpPayloadParser.feed_data', 'aiohttp.streams.StreamReader.feed_data']

/src/aiohttp/fuzz_http_payload_parser.py

Dictionary

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

Fuzzer function priority

Use one of these functions as input to libfuzzer with flag: -focus_function name

-focus_function=['aiohttp.http_parser.HttpPayloadParser.feed_data', 'aiohttp.streams.StreamReader.feed_data']

/src/aiohttp/fuzz_http_parser_pure_python.py

Dictionary

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

/src/aiohttp/fuzz_web_request.py

Dictionary

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

Fuzzer function priority

Use one of these functions as input to libfuzzer with flag: -focus_function name

-focus_function=['multidict._multidict_py.MultiDictProxy.__init__', 'multidict._multidict_py.MultiDict._extend', 'aiohttp.test_utils.make_mocked_request', 'multidict._multidict_py._Base.items', 'aiohttp.web_urldispatcher.UrlMappingMatchInfo.__init__']

/src/aiohttp/fuzz_multipart.py

Dictionary

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

/src/aiohttp/fuzz_payload_url.py

Dictionary

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

Fuzzer function priority

Use one of these functions as input to libfuzzer with flag: -focus_function name

-focus_function=['multidict._multidict_py.MultiDictProxy.__init__', 'multidict._multidict_py.MultiDict._extend', 'aiohttp.payload.StringPayload.__init__']

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
aiohttp.web._run_app._wait	38	0	0.0%	[]
aiohttp.web_request.BaseRequest.forwarded	32	3	9.375%	[]
aiohttp.web_request.BaseRequest.post	56	4	7.142%	['fuzz_web_request']
aiohttp.client_reqrep.ClientRequest.__init__	42	0	0.0%	[]
aiohttp.client_reqrep.ClientRequest.send	36	0	0.0%	[]
out.getvalue	116	39	33.62%	[]
aiohttp.http_websocket.ws_ext_parse	31	4	12.90%	[]
aiohttp.http_websocket.WebSocketReader._feed_data	56	0	0.0%	[]
aiohttp.http_websocket.WebSocketReader.parse_frame	83	10	12.04%	[]
aiohttp.http_websocket.WebSocketWriter._send_frame	39	0	0.0%	[]
aiohttp.multipart.parse_content_disposition.unescape	53	0	0.0%	[]
aiohttp.client.ClientSession.__init__	49	2	4.081%	[]
aiohttp.client.ClientSession._request	167	20	11.97%	[]
aiohttp.client.ClientSession._ws_connect	70	14	20.0%	[]
aiohttp.connector.BaseConnector.connect	58	0	0.0%	[]
aiohttp.connector.TCPConnector._resolve_host	43	0	0.0%	[]
aiohttp.connector.TCPConnector._create_direct_connection.drop_exception	33	0	0.0%	[]
aiohttp.connector.TCPConnector._create_proxy_connection	46	2	4.347%	[]
aiohttp.cookiejar.CookieJar.update_cookies	46	0	0.0%	[]
aiohttp.cookiejar.CookieJar.filter_cookies	41	0	0.0%	[]
aiohttp.cookiejar.CookieJar._parse_date	49	2	4.081%	[]
aiohttp.client_proto.ResponseHandler.data_received	37	0	0.0%	[]
aiohttp.client_ws.ClientWebSocketResponse.close	38	0	0.0%	[]
aiohttp.client_ws.ClientWebSocketResponse.receive	50	0	0.0%	[]
aiohttp.web_response.StreamResponse._prepare_headers	44	0	0.0%	[]
aiohttp.web_response.Response.__init__	39	2	5.128%	[]
aiohttp.web_fileresponse.FileResponse.prepare	73	0	0.0%	[]
aiodns.DNSResolver	107	29	27.10%	[]
aiohttp.web_protocol.RequestHandler.__init__	34	0	0.0%	[]
aiohttp.web_protocol.RequestHandler.start	77	0	0.0%	[]
aiohttp.web_ws.WebSocketResponse._handshake	35	0	0.0%	[]
aiohttp.web_ws.WebSocketResponse.close	44	0	0.0%	[]
aiohttp.web_ws.WebSocketResponse.receive	52	0	0.0%	[]

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
	[]	[]
aiohttp.client_proto	[]	[]
os	[]	[]
re	[]	[]
aiohttp.abc	[]	[]
ipaddress	[]	[]
mimetypes	[]	[]
uuid	[]	[]
idna	[]	[]
aiohttp.test_utils	['fuzz_web_request']	[]
aiohttp.streams	['fuzz_http_payload_parser_pure_python', 'fuzz_http_payload_parser']	[]
argparse	[]	[]
aiohttp.http_writer	[]	[]
platform	[]	[]
aiohttp.cookiejar	[]	[]
hashlib	[]	[]
	[]	[]
aiohttp.connector	[]	[]
ssl	[]	[]
aiohttp.web	[]	[]
aiohttp.tracing	[]	[]
aiohttp.tcp_helpers	[]	[]
weakref	[]	[]
textwrap	[]	[]
aiohttp.compression_utils	['fuzz_http_payload_parser_pure_python', 'fuzz_http_payload_parser', 'fuzz_multipart']	[]
enum	[]	[]
aiodns	[]	[]
codecs	[]	[]
base64	[]	[]
aiohttp.web_response	[]	[]
yarl._url	[]	[]
aiohttp.worker	[]	[]
ClientSession	[]	[]
multidict._multidict_base	[]	[]
aiohttp.payload	['fuzz_payload_url']	[]
dataclasses	[]	[]
gc	[]	[]
aiohappyeyeballs	[]	[]
functools	[]	[]
warnings	[]	[]
_http_parser	[]	[]
_websocket	[]	[]
aiohttp.web_middlewares	[]	[]
inspect	[]	[]
logging	[]	[]
types	[]	[]
_multidict	[]	[]
aiohttp.formdata	[]	[]
multidict	[]	[]
async_timeout	[]	[]
email	[]	[]
...aiohttp.fuzz_http_payload_parser_pure_python	['fuzz_http_payload_parser_pure_python']	[]
aiohttp	[]	[]
aiohttp.log	[]	[]
array	[]	[]
aiosignal	[]	[]
aiohttp.http	[]	[]
atheris	[]	[]
importlib	[]	[]
uvloop	[]	[]
multidict._abc	[]	[]
aiohttp.client	[]	[]
...aiohttp.fuzz_http_parser_pure_python	['fuzz_http_parser_pure_python']	[]
socket	[]	[]
sys	[]	[]
keyword	[]	[]
aiohttp.web_exceptions	[]	[]
collections	[]	[]
aiohttp.hdrs	[]	[]
time	[]	[]
aiohttp.helpers	['fuzz_http_payload_parser_pure_python', 'fuzz_http_payload_parser', 'fuzz_web_request', 'fuzz_multipart', 'fuzz_payload_url']	[]
aiohttp.web_fileresponse	[]	[]
itertools	[]	[]
aiohttp.http_websocket	[]	[]
contextlib	[]	[]
frozenlist	[]	[]
aiohttp.web_protocol	[]	[]
aiohttp.client_exceptions	[]	[]
asyncio	[]	[]
yarl._quoting	[]	[]
aiohttp.web_ws	[]	[]
zlib	[]	[]
io	[]	[]
aiohttp.pytest_plugin	[]	[]
gunicorn	[]	[]
abc	[]	[]
aiohttp.http_exceptions	['fuzz_http_payload_parser_pure_python', 'fuzz_http_payload_parser']	[]
aiohttp.web_runner	[]	[]
yarl	[]	[]
multidict._compat	[]	[]
aiohttp.typedefs	[]	[]
random	[]	[]
...aiohttp.fuzz_web_request	['fuzz_web_request']	[]
aiohttp.locks	[]	[]
calendar	[]	[]
html	[]	[]
typing	[]	[]
pathlib	[]	[]
datetime	[]	[]
aiohttp.multipart	['fuzz_web_request', 'fuzz_multipart']	[]
tempfile	[]	[]
aiohttp.client_reqrep	['fuzz_multipart']	[]
brotli	[]	[]
signal	[]	[]
aiohttp.base_protocol	[]	[]
aiohttp.web_request	['fuzz_web_request']	[]
aiohttp.client_ws	[]	[]
aiohttp.web_log	[]	[]
...aiohttp.fuzz_http_parser	['fuzz_http_parser']	[]
multidict._multidict_py	['fuzz_web_request', 'fuzz_payload_url']	[]
yarl._quoting_py	[]	[]
struct	[]	[]
aiohttp.web_urldispatcher	['fuzz_web_request']	[]
string	[]	[]
binascii	[]	[]
_helpers	[]	[]
netrc	[]	[]
pickle	[]	[]
...aiohttp.fuzz_payload_url	['fuzz_payload_url']	[]
aiohttp.web_routedef	[]	[]
math	[]	[]
aiohttp.web_app	[]	[]
...aiohttp.fuzz_http_payload_parser	['fuzz_http_payload_parser']	[]
http	[]	[]
aiohttp.resolver	[]	[]
unittest	[]	[]
aiohttp.http_parser	['fuzz_http_payload_parser_pure_python', 'fuzz_http_payload_parser']	[]
_quoting_c	[]	[]
json	[]	[]
brotlicffi	[]	[]
_abc	[]	[]
traceback	[]	[]
urllib	[]	[]
...aiohttp.fuzz_multipart	['fuzz_multipart']	[]
aiohttp.web_server	[]	[]

Directories in report

Directory