High level conclusions

Fuzzer fuzz_future_urllib is blocked:

The runtime code coverage of fuzz_future_urllib 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_future_email is blocked:

The runtime code coverage of fuzz_future_email covers 26.76% 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_past is blocked:

The runtime code coverage of fuzz_past covers 21.42% 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

55 / 1694

Cyclomatic complexity statically reachable by fuzzers

238 / 5962

Runtime code coverage of functions

233 / 1694

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_past

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	10	55.5%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	8	44.4%
All colors	18	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
4	2	...fuzz_past.fuzz_dict	call site: 00002	json.loads
3	13	...fuzz_past.fuzz_str	call site: 00013	past.types.oldstr.unescape
2	7	...fuzz_past.fuzz_dict	call site: 00007	...fuzz_past.fuzz_str
1	0	EP	call site: 00000	...fuzz_past.fuzz_dict

Runtime coverage analysis

Covered functions

12

Functions that are reachable but not covered

11

Reachable functions

14

Percentage of reachable functions covered

21.43%

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_past	12
past.types.oldstr	1

Fuzzer: fuzz_future_email

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	46	35.9%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	82	64.0%
All colors	128	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
14	66	future.backports.email.message.Message._get_params_preserve	call site: 00066	builtins.list
8	43	future.backports.email.charset.Charset.__init__	call site: 00043	future.backports.email.header.Header.append
5	93	future.backports.email.message._unquotevalue	call site: 00093	future.backports.email.message.Message.get
4	20	future.backports.email.message.Message.add_header	call site: 00020	future.backports.email.message.Message.set_boundary
3	31	future.backports.email._policybase.Compat32._sanitize_header	call site: 00031	future.backports.email.header.Header.__init__
3	100	future.backports.email.message.Message.set_charset	call site: 00100	future.backports.email.message.Message.add_header
2	9	future.backports.email.message.Message.add_header	call site: 00009	k.replace
2	87	future.backports.email.message.Message.set_payload	call site: 00087	future.backports.email.message.Message.del_param
2	113	future.backports.email.message.Message.get_param	call site: 00113	future.backports.email.message._formatparam
1	36	future.backports.email.charset.Charset.__init__	call site: 00036	builtins.str
1	56	future.backports.email.message._parseparam	call site: 00056	s.find
1	123	future.backports.email.message.Message.set_charset	call site: 00123	charset.body_encode

Runtime coverage analysis

Covered functions

289

Functions that are reachable but not covered

52

Reachable functions

71

Percentage of reachable functions covered

26.76%

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_future_email	5
future.backports.email.mime.multipart	3
future.backports.email.mime.base	2
future.backports.email.message	49
future.backports.email._policybase	3
future.backports.email.header	6
future.backports.email.charset	7
future.backports.email.mime.text	3

Fuzzer: fuzz_future_htmlparser

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	64	36.7%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	110	63.2%
All colors	174	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
33	106	future.backports._markupbase.ParserBase.parse_marked_section	call site: 00106	future.backports._markupbase.ParserBase._parse_doctype_subset
5	21	future.backports.html.parser.HTMLParser.check_for_whole_start_tag	call site: 00021	future.backports._markupbase.ParserBase.updatepos
4	81	future.backports.html.parser.HTMLParser.parse_pi	call site: 00081	future.backports._markupbase.ParserBase.parse_declaration
4	146	future.backports.html.parser.HTMLParser.goahead	call site: 00146	future.backports.html.parser.HTMLParser.error
4	169	future.backports.html.parser.HTMLParser.goahead	call site: 00169	future.backports._markupbase.ParserBase.updatepos
2	54	future.backports.html.parser.HTMLParser.parse_endtag	call site: 00054	future.backports.html.parser.HTMLParser.handle_data
2	70	future.backports.html.parser.HTMLParser.goahead	call site: 00070	future.backports._markupbase.ParserBase.error
2	165	future.backports.html.parser.HTMLParser.goahead	call site: 00165	future.backports._markupbase.ParserBase.updatepos
1	0	EP	call site: 00000	atheris.FuzzedDataProvider
1	2	...fuzz_future_htmlparser.TestOneInput	call site: 00002	warnings.warn
1	17	future.backports.html.parser.HTMLParser.parse_starttag	call site: 00017	locatestarttagend.match
1	29	future.backports.html.parser.HTMLParser.parse_starttag	call site: 00029	attrfind.match

Runtime coverage analysis

Covered functions

289

Functions that are reachable but not covered

48

Reachable functions

78

Percentage of reachable functions covered

38.46%

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_future_htmlparser	5
future.backports.html.parser	57
future.backports._markupbase	26

Fuzzer: fuzz_future_urllib

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	10	30.3%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	23	69.6%
All colors	33	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
4	2	...fuzz_future_urllib.TestOneInput	call site: 00002	future.backports.urllib.request.parse_http_list
2	18	future.backports.urllib.parse.quote_from_bytes	call site: 00018	builtins.bytes
2	27	future.backports.urllib.parse.quote_from_bytes	call site: 00027	fdp.ConsumeIntInRange
1	9	future.backports.urllib.request.parse_http_list	call site: 00009	future.backports.urllib.parse.quote
1	14	future.backports.urllib.parse.quote_from_bytes	call site: 00014	builtins.str

Runtime coverage analysis

Covered functions

290

Functions that are reachable but not covered

16

Reachable functions

20

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
...fuzz_future_urllib	7
future.backports.urllib.request	2
future.backports.urllib.parse	10

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
future.backports.urllib.request.URLopener.retrieve	future.backports.urllib.request	5	['N/A', 'N/A', 'N/A', 'N/A', 'N/A']	4	0	8	9	7	198	0	661	435
future.backports.http.cookiejar.CookieJar.make_cookies	future.backports.http.cookiejar	3	['N/A', 'N/A', 'N/A']	4	0	5	4	5	115	2	389	307
future.backports.email.headerregistry.AddressHeader.parse	future.backports.email.headerregistry	3	['N/A', 'N/A', 'N/A']	6	0	1	3	4	105	0	369	299
future.backports.http.server.CGIHTTPRequestHandler.run_cgi	future.backports.http.server	1	['N/A']	3	0	25	31	15	98	2	321	262
future.backports.http.client.HTTPConnection._send_request	future.backports.http.client	5	['N/A', 'N/A', 'N/A', 'N/A', 'N/A']	7	0	4	4	5	79	1	270	163
future.backports.urllib.robotparser.RobotFileParser.read	future.backports.urllib.robotparser	1	['N/A']	4	0	2	2	4	101	0	343	154
future.backports.xmlrpc.client.Transport.request	future.backports.xmlrpc.client	5	['N/A', 'N/A', 'N/A', 'N/A', 'N/A']	4	0	0	2	4	66	0	216	136

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

Functions statically reachable by fuzzers

253 / 1694

Cyclomatic complexity statically reachable by fuzzers

1029 / 5962

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 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
s.encode	89	32	35.95%	['fuzz_past', 'fuzz_future_email']
y.decode	275	80	29.09%	[]
future.utils.exec_	268	67	25.0%	[]
future.backports.email.message.Message.get_payload	44	10	22.72%	[]
future.builtins.misc.pow	34	16	47.05%	[]
future.backports.email.header.decode_header	61	0	0.0%	[]
future.backports.email.header.Header.encode	39	0	0.0%	[]
future.backports.email.feedparser.FeedParser._parsegen	171	0	0.0%	[]
future.backports.email.feedparser.FeedParser._parse_headers	34	2	5.882%	[]
future.backports._markupbase.ParserBase.parse_declaration	44	0	0.0%	['fuzz_future_htmlparser']
future.backports._markupbase.ParserBase._parse_doctype_subset	54	0	0.0%	['fuzz_future_htmlparser']
future.backports._markupbase.ParserBase._parse_doctype_attlist	44	0	0.0%	[]
future.backports.email.utils.decode_params	34	15	44.11%	[]
future.backports.email._parseaddr._parsedate_tz	86	0	0.0%	[]
future.backports.email._parseaddr.AddrlistClass.getaddress	38	0	0.0%	[]
future.backports.datetime._wrap_strftime	47	0	0.0%	[]
future.backports.urllib.parse.urlsplit	42	0	0.0%	[]
future.backports.urllib.parse.urljoin	39	0	0.0%	[]
future.backports.urllib.parse.urlencode	39	0	0.0%	[]
future.standard_library.install_aliases	54	0	0.0%	[]
future.backports.urllib.request.urlretrieve	31	0	0.0%	[]
future.backports.urllib.request.OpenerDirector.add_handler	36	0	0.0%	[]
future.backports.urllib.request.AbstractDigestAuthHandler.get_authorization	40	0	0.0%	[]
future.backports.urllib.request.AbstractHTTPHandler.do_request_	32	0	0.0%	[]
future.backports.urllib.request.FTPHandler.ftp_open	45	0	0.0%	[]
future.backports.urllib.request.URLopener.retrieve	51	0	0.0%	[]
future.backports.urllib.request.URLopener._open_generic_http	53	0	0.0%	[]
future.backports.urllib.request.URLopener.open_ftp	50	0	0.0%	[]
future.backports.urllib.request.ftpwrapper.retrfile	37	0	0.0%	[]
future.backports.urllib.request._proxy_bypass_macosx_sysconf.ip2num	32	1	3.125%	[]
future.backports.urllib.request.proxy_bypass_registry	38	0	0.0%	[]
future.backports.http.client.HTTPResponse.begin	45	0	0.0%	[]
future.backports.http.client.HTTPConnection.send	33	0	0.0%	[]
future.backports.http.client.HTTPConnection.putrequest	34	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
	[]	[]
future.backports.urllib.error	[]	[]
future.backports._markupbase	['fuzz_future_htmlparser']	[]
getpass	[]	[]
future.moves.urllib.request	[]	[]
future.backports.email.message	['fuzz_future_email']	[]
future.moves.tkinter.dnd	[]	[]
future.moves.xmlrpc.client	[]	[]
future.backports.xmlrpc.client	[]	[]
marshal	[]	[]
future.backports.http.cookiejar	[]	[]
mimetypes	[]	[]
past.builtins.noniterators	[]	[]
future.types	[]	[]
socket	[]	[]
future.types.newobject	[]	[]
future.backports.html.parser	['fuzz_future_htmlparser']	[]
itertools	[]	[]
future.backports.email.mime.nonmultipart	[]	[]
operator	[]	[]
subprocess	[]	[]
future	[]	[]
future.backports.email.mime.multipart	['fuzz_future_email']	[]
calendar	[]	[]
	[]	[]
lib2to3	[]	[]
future.builtins.disabled	[]	[]
future.moves.tkinter.font	[]	[]
future.moves.xmlrpc.server	[]	[]
future.backports.html.entities	[]	[]
future.backports.urllib.robotparser	[]	[]
future.types.newbytes	[]	[]
sys	[]	[]
future.builtins.misc	[]	[]
future.backports.email.mime.text	['fuzz_future_email']	[]
...fuzz_past	['fuzz_past']	[]
future.backports.urllib.parse	['fuzz_future_urllib']	[]
future.moves.http.cookiejar	[]	[]
future.backports	[]	[]
pydoc	[]	[]
logging	[]	[]
future.moves.tkinter.scrolledtext	[]	[]
future.types.newopen	[]	[]
past.translation	[]	[]
select	[]	[]
io	[]	[]
...fuzz_future_email	['fuzz_future_email']	[]
future.moves.html.parser	[]	[]
past.types.basestring	[]	[]
future.moves.tkinter.tix	[]	[]
future.types.newmemoryview	[]	[]
future.moves.tkinter.dialog	[]	[]
past.builtins	[]	[]
nturl2path	[]	[]
future.backports.email.iterators	[]	[]
_dummy_thread	[]	[]
...fuzz_future_htmlparser	['fuzz_future_htmlparser']	[]
future.moves.tkinter.commondialog	[]	[]
__builtin__	[]	[]
tempfile	[]	[]
imghdr	[]	[]
future.moves.test.support	[]	[]
future.moves.itertools	[]	[]
future.moves.sys	[]	[]
future.builtins.iterators	[]	[]
future.moves.tkinter.simpledialog	[]	[]
future.backports.email._parseaddr	[]	[]
future.moves.subprocess	[]	[]
future.backports.email.mime.base	['fuzz_future_email']	[]
decimal	[]	[]
future.backports.email	[]	[]
future.types.newint	[]	[]
dummy_threading	[]	[]
future.moves.tkinter.ttk	[]	[]
...fuzz_future_urllib	['fuzz_future_urllib']	[]
past	[]	[]
future.backports.http.server	[]	[]
future.moves.copyreg	[]	[]
future.backports.urllib.request	['fuzz_future_urllib']	[]
_strptime	[]	[]
importlib	[]	[]
future.moves.urllib.response	[]	[]
future.builtins.newnext	[]	[]
future.backports.email.errors	[]	[]
future.moves._thread	[]	[]
ssl	[]	[]
future.moves.tkinter.messagebox	[]	[]
future.backports.urllib.response	[]	[]
datetime	[]	[]
future.utils.surrogateescape	[]	[]
future.types.newrange	[]	[]
functools	[]	[]
atheris	[]	[]
future.moves._dummy_thread	[]	[]
os	[]	[]
sndhdr	[]	[]
hashlib	[]	[]
future.moves.configparser	[]	[]
future.backports.email.base64mime	[]	[]
future.standard_library	[]	[]
future.backports.email._header_value_parser	[]	[]
time	[]	[]
posixpath	[]	[]
future.moves	[]	[]
past.types.oldstr	['fuzz_past']	[]
shutil	[]	[]
base64	[]	[]
future.moves.dbm.dumb	[]	[]
future.backports.http.client	[]	[]
collections	[]	[]
future.moves.dbm.gnu	[]	[]
future.builtins	[]	[]
future.backports.total_ordering	[]	[]
future.builtins.newround	[]	[]
future.backports.xmlrpc.server	[]	[]
future.backports.email.policy	[]	[]
future.moves.html	[]	[]
heapq	[]	[]
future.backports.email.quoprimime	[]	[]
_weakref	[]	[]
warnings	[]	[]
_scproxy	[]	[]
future.backports.email.mime.audio	[]	[]
future.backports.email.mime.application	[]	[]
future.moves.queue	[]	[]
future.moves.http.cookies	[]	[]
pwd	[]	[]
types	[]	[]
future.backports.email.mime.image	[]	[]
future.backports.email.feedparser	[]	[]
future.backports.email.parser	[]	[]
uu	[]	[]
future.backports.email.utils	[]	[]
future.utils	[]	[]
_socket	[]	[]
future.moves.urllib.robotparser	[]	[]
future.builtins.new_min_max	[]	[]
thread	[]	[]
future.backports.email.mime.message	[]	[]
future.backports.email.header	['fuzz_future_email']	[]
future.backports.http.cookies	[]	[]
future.moves.pickle	[]	[]
imp	[]	[]
ftplib	[]	[]
binascii	[]	[]
future.backports.email.mime	[]	[]
builtins	[]	[]
inspect	[]	[]
future.types.newstr	[]	[]
future.moves.dbm.ndbm	[]	[]
fcntl	[]	[]
future.backports.urllib	[]	[]
future.backports.html	[]	[]
copy	[]	[]
future.moves.builtins	[]	[]
future.moves.xmlrpc	[]	[]
future.moves.urllib.parse	[]	[]
re	[]	[]
future.backports.email._encoded_words	[]	[]
quopri	[]	[]
future.moves.test	[]	[]
past.utils	[]	[]
future.backports.email.encoders	[]	[]
future.moves.http	[]	[]
future.moves.http.server	[]	[]
past.builtins.misc	[]	[]
future.backports.socket	[]	[]
reprlib	[]	[]
future.backports.http	[]	[]
future.moves.urllib.error	[]	[]
string	[]	[]
fnmatch	[]	[]
future.moves.urllib	[]	[]
future.backports.email._policybase	['fuzz_future_email']	[]
threading	[]	[]
future.moves.tkinter.constants	[]	[]
past.types	[]	[]
winreg	[]	[]
bisect	[]	[]
dummy_thread	[]	[]
_thread	[]	[]
future.builtins.newsuper	[]	[]
future.backports.email.headerregistry	[]	[]
future.moves.html.entities	[]	[]
future.moves.http.client	[]	[]
contextlib	[]	[]
future.backports.email.generator	[]	[]
math	[]	[]
future.moves.winreg	[]	[]
future.backports.xmlrpc	[]	[]
future.backports.datetime	[]	[]
abc	[]	[]
codecs	[]	[]
future.backports.misc	[]	[]
future.backports.email.charset	['fuzz_future_email']	[]
argparse	[]	[]
xml	[]	[]
random	[]	[]
future.moves.tkinter.colorchooser	[]	[]
future.moves.collections	[]	[]
future.moves.tkinter	[]	[]
gzip	[]	[]
future.moves.socketserver	[]	[]
past.types.olddict	[]	[]
future.moves.tkinter.filedialog	[]	[]
future.moves.reprlib	[]	[]
traceback	[]	[]
future.moves._markupbase	[]	[]
future.types.newlist	[]	[]
future.moves.dbm	[]	[]
future.backports.socketserver	[]	[]
json	[]	[]
future.types.newdict	[]	[]

Directories in report

Directory