High level conclusions

Fuzzers reach 70.90% code coverage.

Fuzzers reach 88.07% of cyclomatic complexity.

Fuzzers reach 77.32% of all functions.

Reachability and coverage overview

Functions statically reachable by fuzzers

2166 / 2801

Cyclomatic complexity statically reachable by fuzzers

28446 / 32298

Runtime code coverage of functions

1986 / 2801

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

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	99	22.6%
gold	[1:9]	48	10.9%
yellow	[10:29]	7	1.60%
greenyellow	[30:49]	5	1.14%
lawngreen	50+	278	63.6%
All colors	437	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	123	xmlVRaiseError	call site: 00123	xmlFormatError
10	409	xmlRegEpxFromParse	call site: 00409	xmlRegexpErrMemory
8	9	xmlInitRandom	call site: 00009	xmlAbort
7	101	xmlVRaiseError	call site: 00101	xmlGetLineNo
5	169	xmlFAGenerateTransitions	call site: 00169	xmlRegCopyAtom
5	429	xmlFuzzDataCleanup	call site: 00429	xmlDictFree
4	175	xmlRegNewRange	call site: 00175	xmlRegexpErrMemory
3	81	__xmlStructuredError	call site: 00081	__xmlStructuredError
3	119	xmlVSetError	call site: 00119	xmlCopyError
3	180	xmlRegFreeAtom	call site: 00180	xmlFAGenerateTransitions
3	318	xmlFACompareAtoms	call site: 00318	xmlRegStrEqualWildcard
2	113	xmlStrVASPrintf	call site: 00113	xmlStrdup

Runtime coverage analysis

Covered functions

147

Functions that are reachable but not covered

41

Reachable functions

182

Percentage of reachable functions covered

77.47%

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
fuzz/regexp.c	1
fuzz/fuzz.c	6
hash.c	4
threads.c	7
dict.c	6
error.c	13
xmlmemory.c	1
globals.c	12
encoding.c	1
xpath.c	2
xmlIO.c	1
catalog.c	1
xmlschemastypes.c	1
relaxng.c	1
xmlregexp.c	60
xmlstring.c	7
./include/private/memory.h	1
tree.c	2
parserInternals.c	1
chvalid.c	1
./codegen/unicode.inc	35

Fuzzer: uri

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	41	12.4%
gold	[1:9]	41	12.4%
yellow	[10:29]	10	3.03%
greenyellow	[30:49]	4	1.21%
lawngreen	50+	234	70.9%
All colors	330	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
8	9	xmlInitRandom	call site: 00009	xmlAbort
7	218	xmlURIEscape	call site: 00218	xmlURIEscapeStr
5	323	xmlFuzzDataCleanup	call site: 00323	xmlDictFree
4	134	LLVMFuzzerTestOneInput	call site: 00134	fprintf
4	197	xmlURIEscape	call site: 00197	xmlURIEscapeStr
2	150	xmlSaveUri	call site: 00150	xmlSaveUriRealloc
2	159	xmlSaveUri	call site: 00159	xmlSaveUriRealloc
1	27	xmlInitGlobalsInternal	call site: 00027	xmlResetError
1	45	xmlGetThreadLocalStorage	call site: 00045	pthread_getspecific
1	47	xmlGetThreadLocalStorage	call site: 00047	xmlAbort
1	60	xmlRandom	call site: 00060	xmlHashGrow
1	85	xmlParse3986Host	call site: 00085	xmlParse3986DecOctet

Runtime coverage analysis

Covered functions

98

Functions that are reachable but not covered

26

Reachable functions

117

Percentage of reachable functions covered

77.78%

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
fuzz/uri.c	1
fuzz/fuzz.c	7
hash.c	4
threads.c	7
dict.c	6
error.c	3
xmlmemory.c	1
globals.c	6
encoding.c	1
xpath.c	2
xmlIO.c	1
catalog.c	1
xmlschemastypes.c	1
relaxng.c	1
uri.c	43
xmlstring.c	12
./include/private/memory.h	1

Fuzzer: html

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	567	45.6%
gold	[1:9]	38	3.05%
yellow	[10:29]	13	1.04%
greenyellow	[30:49]	4	0.32%
lawngreen	50+	620	49.9%
All colors	1242	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
73	906	xmlHashUpdateInternal	call site: 00906	xmlCopyEntity
40	1027	xmlNewDocProp	call site: 01027	xmlNewDocProp
26	694	xmlAllocOutputBuffer	call site: 00694	xmlCharEncOutput
24	166	xmlUnlinkNode	call site: 00166	xmlFreeEntitiesTable
19	982	xmlNewDocProp	call site: 00982	xmlNodeParseAttValue
19	1122	xmlNodeGetContent	call site: 01122	xmlBufGetNodeContent
18	1006	xmlNewText	call site: 01006	xmlNodeParseAttValue
15	320	xmlVRaiseError	call site: 00320	xmlRaiseMemoryError
14	761	htmlNodeDumpInternal	call site: 00761	htmlParseMetaEncoding
13	1068	xmlCopyPropInternal	call site: 01068	xmlSetTreeDoc
12	779	htmlNodeDumpInternal	call site: 00779	xmlNsListDumpOutput
11	137	xmlFreeDtd	call site: 00137	xmlFreeElementTable

Runtime coverage analysis

Covered functions

302

Functions that are reachable but not covered

143

Reachable functions

389

Percentage of reachable functions covered

63.24%

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
fuzz/html.c	1
fuzz/fuzz.c	7
hash.c	16
threads.c	7
dict.c	18
error.c	14
xmlmemory.c	1
globals.c	15
encoding.c	19
xpath.c	2
xmlIO.c	17
catalog.c	5
xmlschemastypes.c	1
relaxng.c	1
HTMLparser.c	56
SAX2.c	1
parserInternals.c	30
parser.c	9
buf.c	19
tree.c	50
valid.c	33
list.c	3
xmlregexp.c	4
entities.c	8
xmlstring.c	12
./include/private/memory.h	1
./include/private/parser.h	1
HTMLtree.c	9
xmlsave.c	3

Fuzzer: xml

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	966	30.4%
gold	[1:9]	120	3.78%
yellow	[10:29]	57	1.79%
greenyellow	[30:49]	33	1.04%
lawngreen	50+	1992	62.8%
All colors	3168	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
73	1895	xmlBuildURISafe	call site: 01895	xmlCatalogXMLResolve
70	811	xmlRMutexUnlock	call site: 00811	xmlCatalogListXMLResolve
61	2646	htmlIsBooleanAttr	call site: 02646	htmlAttrDumpOutput
56	1977	xmlInitializeCatalog	call site: 01977	xmlACatalogResolve
35	1615	xmlCopyNamespaceList	call site: 01615	xmlCopyDtd
35	2588	xmlOutputBufferWriteQuotedString	call site: 02588	htmlNodeDumpInternal
27	1804	xmlStrncat	call site: 01804	xmlParseXMLCatalogOneNode
19	1709	xmlNodeGetContent	call site: 01709	xmlBufGetNodeContent
18	1278	xmlParseAttValue	call site: 01278	xmlSkipBlankChars
17	1569	xmlCopyPropInternal	call site: 01569	xmlNewReconciledNs
17	1778	xmlGetPropNodeValueInternal	call site: 01778	xmlParseXMLCatalogNodeList
16	1651	xmlCreateEnumeration	call site: 01651	xmlCopyEntitiesTable

Runtime coverage analysis

Covered functions

605

Functions that are reachable but not covered

169

Reachable functions

697

Percentage of reachable functions covered

75.75%

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
fuzz/xml.c	1
fuzz/fuzz.c	13
hash.c	29
threads.c	9
dict.c	21
error.c	16
xmlmemory.c	1
globals.c	23
encoding.c	19
xpath.c	2
xmlIO.c	31
catalog.c	37
xmlschemastypes.c	1
relaxng.c	1
xmlstring.c	17
parserInternals.c	43
SAX2.c	6
parser.c	153
buf.c	25
tree.c	67
valid.c	40
list.c	3
xmlregexp.c	4
entities.c	10
HTMLparser.c	4
./include/private/memory.h	1
chvalid.c	1
./include/private/parser.h	2
uri.c	35
xmlsave.c	35
HTMLtree.c	8

Fuzzer: valid

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	882	27.4%
gold	[1:9]	96	2.98%
yellow	[10:29]	79	2.45%
greenyellow	[30:49]	32	0.99%
lawngreen	50+	2126	66.1%
All colors	3215	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
86	2631	xmlFACompareAtoms	call site: 02631	xmlFARecurseDeterminism
73	1894	xmlBuildURISafe	call site: 01894	xmlCatalogXMLResolve
70	810	xmlRMutexUnlock	call site: 00810	xmlCatalogListXMLResolve
56	1976	xmlInitializeCatalog	call site: 01976	xmlACatalogResolve
36	2748	xmlRegStateAddTransTo	call site: 02748	xmlFAGenerateTransitions
35	1614	xmlCopyNamespaceList	call site: 01614	xmlCopyDtd
33	1803	xmlStrncat	call site: 01803	xmlParseXMLCatalogOneNode
27	1773	xmlSplitQName4	call site: 01773	xmlParseXMLCatalogNodeList
19	1708	xmlNodeGetContent	call site: 01708	xmlBufGetNodeContent
17	2903	xmlRegExecSetErrString	call site: 02903	xmlFARegExecSaveInputString
15	1594	xmlNewDtd	call site: 01594	xmlCopyEntitiesTable
14	1516	xmlCtxtParseEntity	call site: 01516	xmlSetTreeDoc

Runtime coverage analysis

Covered functions

652

Functions that are reachable but not covered

198

Reachable functions

768

Percentage of reachable functions covered

74.22%

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
fuzz/valid.c	1
fuzz/fuzz.c	13
hash.c	29
threads.c	9
dict.c	21
error.c	16
xmlmemory.c	1
globals.c	20
encoding.c	15
xpath.c	2
xmlIO.c	20
catalog.c	37
xmlschemastypes.c	1
relaxng.c	1
xmlstring.c	16
parserInternals.c	43
SAX2.c	6
parser.c	158
buf.c	19
tree.c	70
valid.c	78
list.c	8
xmlregexp.c	58
entities.c	10
HTMLparser.c	3
./include/private/memory.h	1
chvalid.c	1
./include/private/parser.h	2
uri.c	35
./codegen/unicode.inc	35

Fuzzer: xpath

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	1175	34.9%
gold	[1:9]	161	4.78%
yellow	[10:29]	47	1.39%
greenyellow	[30:49]	26	0.77%
lawngreen	50+	1957	58.1%
All colors	3366	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
131	1811	xmlBuildURISafe	call site: 01811	xmlCatalogXMLResolve
85	1538	xmlNewNs	call site: 01538	xmlStaticCopyNodeList
59	1951	xmlInitializeCatalog	call site: 01951	xmlACatalogResolve
39	715	xmlHashLookup	call site: 00715	xmlParseXMLCatalogFile
32	2195	xmlExpandPEsInEntityValue	call site: 02195	xmlLoadEntityContent
26	1647	xmlNewDoc	call site: 01647	xmlCopyDtd
22	667	xmlRMutexUnlock	call site: 00667	xmlCatalogListXMLResolve
22	1425	nodePush	call site: 01425	xmlParseTextDecl
21	2016	xmlSkipBlankCharsPE	call site: 02016	xmlSkipBlankCharsPE
18	1153	xmlParseAttValue	call site: 01153	xmlSkipBlankChars
18	1752	xmlGetPropNodeValueInternal	call site: 01752	xmlParseXMLCatalogNodeList
17	1508	xmlParseReference	call site: 01508	xmlDocCopyNode

Runtime coverage analysis

Covered functions

689

Functions that are reachable but not covered

190

Reachable functions

763

Percentage of reachable functions covered

75.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
fuzz/xpath.c	1
fuzz/fuzz.c	7
hash.c	28
threads.c	9
dict.c	21
error.c	15
xmlmemory.c	1
globals.c	20
encoding.c	15
xpath.c	140
xmlIO.c	17
catalog.c	37
xmlschemastypes.c	1
relaxng.c	1
parser.c	142
parserInternals.c	40
SAX2.c	6
buf.c	19
HTMLparser.c	2
xmlstring.c	16
tree.c	65
./include/private/memory.h	1
chvalid.c	1
./include/private/parser.h	2
uri.c	35
entities.c	10
valid.c	41
list.c	3
xmlregexp.c	4
xpointer.c	8
./timsort.h	12

Fuzzer: xinclude

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	807	21.6%
gold	[1:9]	238	6.37%
yellow	[10:29]	50	1.33%
greenyellow	[30:49]	64	1.71%
lawngreen	50+	2575	68.9%
All colors	3734	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
70	808	xmlRMutexUnlock	call site: 00808	xmlCatalogListXMLResolve
68	1897	xmlNodeGetBaseSafe	call site: 01897	xmlCatalogXMLResolve
56	1974	xmlInitializeCatalog	call site: 01974	xmlACatalogResolve
18	1275	xmlParseAttValue	call site: 01275	xmlSkipBlankChars
17	1775	xmlGetPropNodeValueInternal	call site: 01775	xmlParseXMLCatalogNodeList
17	1811	xmlGetNsListSafe	call site: 01811	xmlParseXMLCatalogOneNode
14	1260	xmlParseStartTag2	call site: 01260	xmlParseStartTag
14	1376	xmlParseElementEnd	call site: 01376	xmlParseEndTag1
14	1756	xmlFinishDocument	call site: 01756	xmlFreeDoc
13	626	xmlParsePI	call site: 00626	xmlParseCatalogPI
13	1570	xmlSearchNsByHrefSafe	call site: 01570	xmlSearchNsSafe
12	3671	xmlXIncludeLoadTxt	call site: 03671	xmlAddChild

Runtime coverage analysis

Covered functions

813

Functions that are reachable but not covered

133

Reachable functions

826

Percentage of reachable functions covered

83.9%

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
fuzz/xinclude.c	1
fuzz/fuzz.c	12
hash.c	30
threads.c	9
dict.c	21
error.c	15
xmlmemory.c	1
globals.c	20
encoding.c	16
xpath.c	139
xmlIO.c	18
catalog.c	37
xmlschemastypes.c	1
relaxng.c	1
xmlstring.c	18
parserInternals.c	42
SAX2.c	6
parser.c	144
buf.c	19
tree.c	83
valid.c	41
list.c	3
xmlregexp.c	4
entities.c	11
HTMLparser.c	2
./include/private/memory.h	1
chvalid.c	1
./include/private/parser.h	2
uri.c	39
xinclude.c	27
xpointer.c	8
./timsort.h	12

Fuzzer: reader

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	1791	31.4%
gold	[1:9]	285	5.01%
yellow	[10:29]	92	1.61%
greenyellow	[30:49]	48	0.84%
lawngreen	50+	3471	61.0%
All colors	5687	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
277	4540	xmlNodeListGetStringInternal	call site: 04540	xmlTextReaderExpand
153	502	xmlCtxtErrIO	call site: 00502	xmlFreeTextReader
86	4233	xmlFACompareAtoms	call site: 04233	xmlFARecurseDeterminism
68	2679	xmlNodeGetBaseSafe	call site: 02679	xmlCatalogXMLResolve
62	5002	htmlIsBooleanAttr	call site: 05002	xmlSaveSwitchEncoding
60	2859	xmlTextReaderValidatePop	call site: 02859	xmlRelaxNGValidatePopElement
56	2756	xmlInitializeCatalog	call site: 02756	xmlACatalogResolve
37	1492	xmlRMutexUnlock	call site: 01492	xmlCatalogListXMLResolve
36	4350	xmlRegStateAddTransTo	call site: 04350	xmlFAGenerateTransitions
34	4945	xmlOutputBufferWriteQuotedString	call site: 04945	htmlNodeDumpInternal
33	1530	xmlNewParserCtxt	call site: 01530	xmlParserInputBufferCreateFilename
26	4498	xmlTextReaderValidatePush	call site: 04498	xmlRelaxNGValidatePushElement

Runtime coverage analysis

Covered functions

1034

Functions that are reachable but not covered

323

Reachable functions

1202

Percentage of reachable functions covered

73.13%

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
fuzz/reader.c	2
fuzz/fuzz.c	11
hash.c	30
threads.c	9
dict.c	22
error.c	15
xmlmemory.c	2
globals.c	23
encoding.c	19
xpath.c	139
xmlIO.c	30
catalog.c	37
xmlschemastypes.c	2
relaxng.c	58
xmlstring.c	19
xmlreader.c	85
buf.c	20
SAX2.c	6
parser.c	152
parserInternals.c	43
./include/private/memory.h	1
tree.c	89
valid.c	51
list.c	3
xmlregexp.c	59
entities.c	11
uri.c	39
xinclude.c	29
pattern.c	8
HTMLparser.c	4
xmlschemas.c	43
./include/private/parser.h	2
chvalid.c	1
xpointer.c	8
./timsort.h	12
./codegen/unicode.inc	35
xmlsave.c	31
HTMLtree.c	8

Fuzzer: api

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	872	16.7%
gold	[1:9]	171	3.29%
yellow	[10:29]	46	0.88%
greenyellow	[30:49]	12	0.23%
lawngreen	50+	4096	78.8%
All colors	5197	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
86	3831	xmlFACompareAtoms	call site: 03831	xmlFARecurseDeterminism
68	1908	xmlNodeGetBaseSafe	call site: 01908	xmlCatalogXMLResolve
57	1985	xmlInitializeCatalog	call site: 01985	xmlACatalogResolve
36	3948	xmlRegStateAddTransTo	call site: 03948	xmlFAGenerateTransitions
32	2229	xmlExpandPEsInEntityValue	call site: 02229	xmlLoadEntityContent
23	2048	xmlParsePERefInternal	call site: 02048	xmlSkipBlankCharsPE
22	805	xmlRMutexUnlock	call site: 00805	xmlCatalogListXMLResolve
20	1461	xmlCtxtParseContentInternal	call site: 01461	xmlParseTextDecl
19	835	xmlHashUpdateInternal	call site: 00835	xmlFetchXMLCatalogFile
17	4103	xmlRegExecSetErrString	call site: 04103	xmlFARegExecSaveInputString
15	1787	xmlGetPropNodeValueInternal	call site: 01787	xmlParseXMLCatalogNodeList
13	630	xmlParsePI	call site: 00630	xmlParseCatalogPI

Runtime coverage analysis

Covered functions

927

Functions that are reachable but not covered

153

Reachable functions

1007

Percentage of reachable functions covered

84.81%

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
fuzz/api.c	35
fuzz/fuzz.c	11
hash.c	31
threads.c	9
dict.c	21
error.c	15
xmlmemory.c	1
globals.c	23
encoding.c	19
xpath.c	2
xmlIO.c	29
catalog.c	37
xmlschemastypes.c	1
relaxng.c	1
tree.c	155
valid.c	101
list.c	12
xmlregexp.c	58
entities.c	20
parser.c	147
parserInternals.c	38
SAX2.c	6
buf.c	26
HTMLparser.c	7
xmlstring.c	18
./include/private/memory.h	1
chvalid.c	1
./include/private/parser.h	2
uri.c	36
HTMLtree.c	20
./codegen/unicode.inc	35
xmlsave.c	49

Fuzzer: lint

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	9311	79.6%
gold	[1:9]	207	1.77%
yellow	[10:29]	79	0.67%
greenyellow	[30:49]	43	0.36%
lawngreen	50+	2052	17.5%
All colors	11692	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
1136	5892	xmlPatternCompileSafe	call site: 05892	xmlSchemaParseRedefine
864	3266	xmlStrcmp	call site: 03266	xmlRelaxReadFile
661	5145	xmlFreePatternInternal	call site: 05145	xmlSchemaParseNewDocWithContext
426	4413	xmlNodeSetContentInternal	call site: 04413	xmlRelaxNGCleanupTree
391	8670	xmlValidGetElemDecl	call site: 08670	xmlTextReaderValidatePush
242	2112	xmlDictLookupHashed	call site: 02112	xmlParseNotationDecl
237	1874	xmlSAX2ErrMemory	call site: 01874	xmlSkipBlankCharsPE
229	10960	xmlNodeDumpOutput	call site: 10960	xmllintShellSetContent
225	9210	xmllintMain	call site: 09210	xmlSchemaValidateStream
212	9436	xmlNewNsProp	call site: 09436	parseHtml
208	1461	xmlLoadResource	call site: 01461	xmlSkipBlankCharsPE
197	4841	xmlHashScan	call site: 04841	xmlRelaxNGParseGrammar

Runtime coverage analysis

Covered functions

788

Functions that are reachable but not covered

1310

Reachable functions

2011

Percentage of reachable functions covered

34.86%

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
fuzz/lint.c	2
xmlmemory.c	9
fuzz/fuzz.c	10
hash.c	31
threads.c	13
dict.c	24
error.c	18
globals.c	25
encoding.c	22
xpath.c	147
xmlIO.c	38
catalog.c	51
xmlschemastypes.c	72
relaxng.c	140
xmlstring.c	20
fuzz/../xmllint.c	30
parser.c	167
parserInternals.c	53
chvalid.c	1
./include/private/memory.h	1
uri.c	40
SAX2.c	7
buf.c	20
tree.c	109
./include/private/parser.h	2
valid.c	90
xmlregexp.c	92
entities.c	11
list.c	12
xmlschemas.c	343
xmlreader.c	48
./codegen/unicode.inc	35
pattern.c	32
HTMLparser.c	62
xinclude.c	29
xpointer.c	8
./timsort.h	12
HTMLtree.c	17
fuzz/../shell.c	21
xmlsave.c	45
c14n.c	39

Fuzzer: schema

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	1587	25.6%
gold	[1:9]	420	6.80%
yellow	[10:29]	175	2.83%
greenyellow	[30:49]	77	1.24%
lawngreen	50+	3917	63.4%
All colors	6176	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
66	2608	xmlBuildURI	call site: 02608	xmlCatalogXMLResolve
57	2683	xmlInitializeCatalog	call site: 02683	xmlACatalogResolve
51	2388	xmlCopyNamespaceList	call site: 02388	xmlCopyDtd
40	5535	xmlSchemaBuildContentModelForElement	call site: 05535	xmlSchemaBuildAContentModel
38	687	xmlStrncmp	call site: 00687	xmlCatalogListXMLResolve
33	2203	xmlNewDocNode	call site: 02203	xmlNodeParseAttValue
32	2060	xmlParseStartTag2	call site: 02060	xmlParseStartTag
27	6053	xmlSchemaValidatorPopElem	call site: 06053	xmlAddChild
23	5896	xmlSchemaVAttributesComplex	call site: 05896	xmlNewProp
19	2478	xmlNodeGetContent	call site: 02478	xmlBufGetNodeContent
19	4783	xmlSchemaGetCanonValue	call site: 04783	xmlSchemaDateNormalize
18	5699	xmlSchemaVDocWalk	call site: 05699	xmlSchemaAssembleByXSI

Runtime coverage analysis

Covered functions

1072

Functions that are reachable but not covered

193

Reachable functions

1206

Percentage of reachable functions covered

84.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.

Function name	source code lines	source lines hit	percentage hit

Files reached

filename	functions hit
fuzz/schema.c	1
fuzz/fuzz.c	11
hash.c	30
threads.c	9
dict.c	21
error.c	16
xmlmemory.c	1
globals.c	20
encoding.c	15
xpath.c	2
xmlIO.c	19
catalog.c	37
xmlschemastypes.c	71
relaxng.c	1
xmlstring.c	20
xmlschemas.c	335
parserInternals.c	43
buf.c	19
xmlregexp.c	89
tree.c	85
SAX2.c	6
parser.c	145
valid.c	45
list.c	7
entities.c	10
HTMLparser.c	2
uri.c	36
./include/private/memory.h	1
chvalid.c	1
./include/private/parser.h	2
pattern.c	29
xmlreader.c	3
./codegen/unicode.inc	35

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
xmlSAX2StartElement	/src/libxml2/SAX2.c	3	['N/A', 'N/A', 'N/A']	22	0	77	15	7	284	0	2946	244
xmlSAX2StartElementNs	/src/libxml2/SAX2.c	9	['N/A', 'N/A', 'N/A', 'N/A', 'int', 'N/A', 'int', 'int', 'N/A']	18	0	982	148	59	254	0	2319	157
xmlXPathSubstringFunction	/src/libxml2/xpath.c	2	['N/A', 'int']	14	0	485	88	34	146	0	930	80
xmlCatalogDump	/src/libxml2/catalog.c	1	['N/A']	26	0	37	9	4	306	0	2851	74
xmlCatalogAdd	/src/libxml2/catalog.c	3	['N/A', 'N/A', 'N/A']	41	0	73	12	5	582	0	7153	59
xmlXPathTranslateFunction	/src/libxml2/xpath.c	2	['N/A', 'int']	14	0	435	72	28	138	0	861	48
xmlParseEntity	/src/libxml2/parser.c	1	['N/A']	38	0	15	3	2	586	0	7148	40

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

Functions statically reachable by fuzzers

2212 / 2801

Cyclomatic complexity statically reachable by fuzzers

29148 / 32298

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

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.

fuzz/regexp.c

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=['xmlVRaiseError', 'xmlRegEpxFromParse', 'xmlInitRandom', 'xmlFAGenerateTransitions', 'xmlFuzzDataCleanup', 'xmlRegNewRange', '__xmlStructuredError', 'xmlVSetError', 'xmlRegFreeAtom']

fuzz/uri.c

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=['xmlInitRandom', 'xmlURIEscape', 'xmlFuzzDataCleanup', 'LLVMFuzzerTestOneInput', 'xmlSaveUri', 'xmlInitGlobalsInternal', 'xmlGetThreadLocalStorage']

fuzz/html.c

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=['xmlHashUpdateInternal', 'xmlNewDocProp', 'xmlAllocOutputBuffer', 'xmlUnlinkNode', 'xmlNodeGetContent', 'xmlNewText', 'xmlVRaiseError', 'htmlNodeDumpInternal', 'xmlCopyPropInternal']

fuzz/xml.c

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=['xmlBuildURISafe', 'xmlRMutexUnlock', 'htmlIsBooleanAttr', 'xmlInitializeCatalog', 'xmlCopyNamespaceList', 'xmlOutputBufferWriteQuotedString', 'xmlStrncat', 'xmlNodeGetContent', 'xmlParseAttValue', 'xmlCopyPropInternal']

fuzz/valid.c

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=['xmlFACompareAtoms', 'xmlBuildURISafe', 'xmlRMutexUnlock', 'xmlInitializeCatalog', 'xmlRegStateAddTransTo', 'xmlCopyNamespaceList', 'xmlStrncat', 'xmlSplitQName4', 'xmlNodeGetContent', 'xmlRegExecSetErrString']

fuzz/xpath.c

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=['xmlBuildURISafe', 'xmlNewNs', 'xmlInitializeCatalog', 'xmlHashLookup', 'xmlExpandPEsInEntityValue', 'xmlNewDoc', 'xmlRMutexUnlock', 'nodePush', 'xmlSkipBlankCharsPE', 'xmlParseAttValue']

fuzz/xinclude.c

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=['xmlRMutexUnlock', 'xmlNodeGetBaseSafe', 'xmlInitializeCatalog', 'xmlParseAttValue', 'xmlGetPropNodeValueInternal', 'xmlGetNsListSafe', 'xmlParseStartTag2', 'xmlParseElementEnd', 'xmlFinishDocument', 'xmlParsePI']

fuzz/reader.c

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=['xmlNodeListGetStringInternal', 'xmlCtxtErrIO', 'xmlFACompareAtoms', 'xmlNodeGetBaseSafe', 'htmlIsBooleanAttr', 'xmlTextReaderValidatePop', 'xmlInitializeCatalog', 'xmlRMutexUnlock', 'xmlRegStateAddTransTo', 'xmlOutputBufferWriteQuotedString']

fuzz/api.c

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=['xmlFACompareAtoms', 'xmlNodeGetBaseSafe', 'xmlInitializeCatalog', 'xmlRegStateAddTransTo', 'xmlExpandPEsInEntityValue', 'xmlParsePERefInternal', 'xmlRMutexUnlock', 'xmlCtxtParseContentInternal', 'xmlHashUpdateInternal', 'xmlRegExecSetErrString']

fuzz/lint.c

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=['xmlPatternCompileSafe', 'xmlStrcmp', 'xmlFreePatternInternal', 'xmlNodeSetContentInternal', 'xmlValidGetElemDecl', 'xmlDictLookupHashed', 'xmlSAX2ErrMemory', 'xmlNodeDumpOutput', 'xmllintMain', 'xmlNewNsProp']

fuzz/schema.c

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=['xmlBuildURI', 'xmlInitializeCatalog', 'xmlCopyNamespaceList', 'xmlSchemaBuildContentModelForElement', 'xmlStrncmp', 'xmlNewDocNode', 'xmlParseStartTag2', 'xmlSchemaValidatorPopElem', 'xmlSchemaVAttributesComplex', 'xmlNodeGetContent']

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
xmlErrString	321	173	53.89%	['reader', 'xpath', 'xml', 'valid', 'xinclude', 'html', 'lint', 'api', 'schema']
xmlCtxtResolveFromCatalog	32	17	53.12%	['reader', 'xpath', 'xml', 'valid', 'xinclude', 'lint', 'api', 'schema']
xmlXPathCacheObjectCopy	31	17	54.83%	['lint', 'xinclude', 'reader', 'xpath']
xmlXPathRunEval	31	14	45.16%	['lint', 'xinclude', 'reader', 'xpath']
xmlTextReaderSetStructuredErrorHandler	39	16	41.02%	['reader']
xmlTextReaderSetup	159	70	44.02%	['reader', 'lint']
xmlIOErr	154	10	6.493%	['reader', 'xpath', 'xml', 'valid', 'xinclude', 'lint', 'api', 'schema']
xmlC14NProcessNode	122	56	45.90%	['lint']
xmlC14NCheckForRelativeNamespaces	31	7	22.58%	['lint']
xmlC14NProcessNamespacesAxis	47	22	46.80%	['lint']
xmlExcC14NProcessNamespacesAxis	108	35	32.40%	['lint']
xmlPatMatch	176	85	48.29%	['reader', 'lint']
xmlValidGetValidElements	64	26	40.62%	['lint']
xmllintResourceLoader	52	16	30.76%	['lint']
streamFile	163	87	53.37%	['lint']
testSAX	49	12	24.48%	['lint']
xmlSchemaItemTypeToStr	44	24	54.54%	['lint', 'schema']
xmlSchemaAddAnnotation	83	12	14.45%	['lint', 'schema']
xmlSchemaCheckSRCRedefineFirst	104	7	6.730%	['lint', 'schema']
xmlSchemaCheckSTPropsCorrect	53	20	37.73%	['lint', 'schema']
xmlSchemaCheckCOSSTRestricts	300	145	48.33%	['lint', 'schema']
xmlSchemaCheckCOSSTDerivedOK	43	20	46.51%	['lint', 'schema']
xmlSchemaCheckAttrUsePropsCorrect	68	12	17.64%	['lint', 'schema']
xmlSchemaCheckSRCCT	93	51	54.83%	['lint', 'schema']
xmlSchemaCheckCOSCTExtends	56	30	53.57%	['lint', 'schema']
xmlSchemaCheckDerivationOKRestriction	98	41	41.83%	['lint', 'schema']
xmlSchemaLookupNamespace	45	14	31.11%	['lint', 'schema']
xmlSchemaValidateElemDecl	87	40	45.97%	['lint', 'schema']
xmlSchemaGetBuiltInType	99	48	48.48%	['lint', 'schema']
xmlSchemaCopyValue	91	32	35.16%	['lint', 'schema']
xmlSchemaGetCanonValue	260	86	33.07%	['lint', 'schema']
xmlSchemaValidateFacetInternal	168	65	38.69%	['lint', 'schema']

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
	[]	[]
/src/libxml2/fuzz/uri.c	['uri']	['uri']
/src/libxml2/globals.c	['regexp', 'uri', 'html', 'xml', 'valid', 'xpath', 'xinclude', 'reader', 'api', 'lint', 'schema']	['regexp', 'uri', 'html', 'xml', 'valid', 'xpath', 'xinclude', 'reader', 'api', 'lint', 'schema']
/src/libxml2/xpointer.c	['xpath', 'xinclude', 'reader', 'lint']	['xpath', 'xinclude', 'reader']
/src/libxml2/fuzz/xml.c	['xml']	['xml']
/src/libxml2/xmlsave.c	['html', 'xml', 'reader', 'api', 'lint']	['xml', 'reader', 'api', 'lint']
/src/libxml2/c14n.c	['lint']	['lint']
/src/libxml2/relaxng.c	['regexp', 'uri', 'html', 'xml', 'valid', 'xpath', 'xinclude', 'reader', 'api', 'lint', 'schema']	['regexp', 'uri', 'html', 'xml', 'valid', 'xpath', 'xinclude', 'reader', 'api', 'lint', 'schema']
/src/libxml2/./include/private/memory.h	['regexp', 'uri', 'html', 'xml', 'valid', 'xpath', 'xinclude', 'reader', 'api', 'lint', 'schema']	[]
/src/libxml2/xmlregexp.c	['regexp', 'html', 'xml', 'valid', 'xpath', 'xinclude', 'reader', 'api', 'lint', 'schema']	['regexp', 'valid', 'reader', 'api', 'schema']
/src/libxml2/fuzz/xpath.c	['xpath']	['xpath']
/src/libxml2/chvalid.c	['regexp', 'xml', 'valid', 'xpath', 'xinclude', 'reader', 'api', 'lint', 'schema']	['regexp', 'xml', 'valid', 'xinclude', 'reader', 'api', 'schema']
/src/libxml2/uri.c	['uri', 'xml', 'valid', 'xpath', 'xinclude', 'reader', 'api', 'lint', 'schema']	['uri', 'xml', 'valid', 'xpath', 'xinclude', 'reader', 'api', 'lint', 'schema']
/src/libxml2/HTMLtree.c	['html', 'xml', 'reader', 'api', 'lint']	['html', 'xml', 'reader', 'api', 'lint']
/src/libxml2/xmlschemas.c	['reader', 'lint', 'schema']	['schema']
/src/libxml2/xmlschemastypes.c	['regexp', 'uri', 'html', 'xml', 'valid', 'xpath', 'xinclude', 'reader', 'api', 'lint', 'schema']	['regexp', 'uri', 'html', 'xml', 'valid', 'xpath', 'xinclude', 'reader', 'api', 'lint', 'schema']
/src/libxml2/fuzz/api.c	['api']	['api']
/src/libxml2/threads.c	['regexp', 'uri', 'html', 'xml', 'valid', 'xpath', 'xinclude', 'reader', 'api', 'lint', 'schema']	['regexp', 'uri', 'html', 'xml', 'valid', 'xpath', 'xinclude', 'reader', 'api', 'lint', 'schema']
/src/libxml2/pattern.c	['reader', 'lint', 'schema']	['lint', 'schema']
/src/libxml2/valid.c	['html', 'xml', 'valid', 'xpath', 'xinclude', 'reader', 'api', 'lint', 'schema']	['html', 'xml', 'valid', 'xpath', 'xinclude', 'reader', 'api', 'lint', 'schema']
/src/libxml2/parser.c	['html', 'xml', 'valid', 'xpath', 'xinclude', 'reader', 'api', 'lint', 'schema']	['html', 'xml', 'valid', 'xpath', 'xinclude', 'reader', 'api', 'lint', 'schema']
/src/libxml2/list.c	['html', 'xml', 'valid', 'xpath', 'xinclude', 'reader', 'api', 'lint', 'schema']	['xml', 'valid', 'xpath', 'xinclude', 'reader', 'api', 'lint', 'schema']
/src/libxml2/fuzz/../xmllint.c	['lint']	[]
/src/libxml2/HTMLparser.c	['html', 'xml', 'valid', 'xpath', 'xinclude', 'reader', 'api', 'lint', 'schema']	['html', 'xml', 'valid', 'xinclude', 'api', 'lint']
/src/libxml2/dict.c	['regexp', 'uri', 'html', 'xml', 'valid', 'xpath', 'xinclude', 'reader', 'api', 'lint', 'schema']	['regexp', 'uri', 'html', 'xml', 'valid', 'xpath', 'xinclude', 'reader', 'api', 'lint', 'schema']
/src/libxml2/fuzz/fuzz.c	['regexp', 'uri', 'html', 'xml', 'valid', 'xpath', 'xinclude', 'reader', 'api', 'lint', 'schema']	['regexp', 'uri', 'html', 'xml', 'valid', 'xpath', 'xinclude', 'reader', 'api', 'lint', 'schema']
/src/libxml2/fuzz/xinclude.c	['xinclude']	['xinclude']
/src/libxml2/fuzz/reader.c	['reader']	['reader']
/src/libxml2/encoding.c	['regexp', 'uri', 'html', 'xml', 'valid', 'xpath', 'xinclude', 'reader', 'api', 'lint', 'schema']	['regexp', 'uri', 'html', 'xml', 'valid', 'xpath', 'xinclude', 'reader', 'api', 'lint', 'schema']
/src/libxml2/fuzz/regexp.c	['regexp']	['regexp']
/src/libxml2/tree.c	['regexp', 'html', 'xml', 'valid', 'xpath', 'xinclude', 'reader', 'api', 'lint', 'schema']	['html', 'xml', 'valid', 'xpath', 'xinclude', 'reader', 'api', 'lint', 'schema']
/src/libxml2/hash.c	['regexp', 'uri', 'html', 'xml', 'valid', 'xpath', 'xinclude', 'reader', 'api', 'lint', 'schema']	['regexp', 'uri', 'html', 'xml', 'valid', 'xpath', 'xinclude', 'reader', 'api', 'lint', 'schema']
/src/libxml2/./codegen/unicode.inc	['regexp', 'valid', 'reader', 'api', 'lint', 'schema']	[]
/src/libxml2/fuzz/valid.c	['valid']	['valid']
/src/libxml2/xmlreader.c	['reader', 'lint', 'schema']	['reader', 'lint']
/src/libxml2/entities.c	['html', 'xml', 'valid', 'xpath', 'xinclude', 'reader', 'api', 'lint', 'schema']	['xml', 'valid', 'xpath', 'xinclude', 'reader', 'api', 'schema']
/src/libxml2/buf.c	['html', 'xml', 'valid', 'xpath', 'xinclude', 'reader', 'api', 'lint', 'schema']	['html', 'xml', 'valid', 'xpath', 'xinclude', 'reader', 'api', 'lint', 'schema']
/src/libxml2/xmlstring.c	['regexp', 'uri', 'html', 'xml', 'valid', 'xpath', 'xinclude', 'reader', 'api', 'lint', 'schema']	['regexp', 'uri', 'html', 'xml', 'valid', 'xpath', 'xinclude', 'reader', 'api', 'lint', 'schema']
/src/libxml2/fuzz/html.c	['html']	['html']
/src/libxml2/./timsort.h	['xpath', 'xinclude', 'reader', 'lint']	[]
/src/libxml2/fuzz/schema.c	['schema']	['schema']
/src/libxml2/SAX2.c	['html', 'xml', 'valid', 'xpath', 'xinclude', 'reader', 'api', 'lint', 'schema']	['html', 'xml', 'valid', 'xpath', 'xinclude', 'reader', 'api', 'lint', 'schema']
/src/libxml2/error.c	['regexp', 'uri', 'html', 'xml', 'valid', 'xpath', 'xinclude', 'reader', 'api', 'lint', 'schema']	['regexp', 'html', 'xml', 'valid', 'xpath', 'xinclude', 'reader', 'api', 'lint', 'schema']
/src/libxml2/xpath.c	['regexp', 'uri', 'html', 'xml', 'valid', 'xpath', 'xinclude', 'reader', 'api', 'lint', 'schema']	['regexp', 'uri', 'html', 'xml', 'valid', 'xpath', 'xinclude', 'reader', 'api', 'lint', 'schema']
/src/libxml2/xinclude.c	['xinclude', 'reader', 'lint']	['xinclude', 'reader', 'lint']
/src/libxml2/xmlmemory.c	['regexp', 'uri', 'html', 'xml', 'valid', 'xpath', 'xinclude', 'reader', 'api', 'lint', 'schema']	['regexp', 'uri', 'html', 'xml', 'valid', 'xpath', 'xinclude', 'reader', 'api', 'lint', 'schema']
/src/libxml2/parserInternals.c	['regexp', 'html', 'xml', 'valid', 'xpath', 'xinclude', 'reader', 'api', 'lint', 'schema']	['html', 'xml', 'valid', 'xpath', 'xinclude', 'reader', 'api', 'lint', 'schema']
/src/libxml2/xmlIO.c	['regexp', 'uri', 'html', 'xml', 'valid', 'xpath', 'xinclude', 'reader', 'api', 'lint', 'schema']	['regexp', 'uri', 'html', 'xml', 'valid', 'xpath', 'xinclude', 'reader', 'api', 'lint', 'schema']
/src/libxml2/fuzz/../shell.c	['lint']	[]
/src/libxml2/fuzz/lint.c	['lint']	['lint']
/src/libxml2/catalog.c	['regexp', 'uri', 'html', 'xml', 'valid', 'xpath', 'xinclude', 'reader', 'api', 'lint', 'schema']	['regexp', 'uri', 'html', 'xml', 'valid', 'xpath', 'xinclude', 'reader', 'api', 'lint', 'schema']
/src/libxml2/./include/private/parser.h	['html', 'xml', 'valid', 'xpath', 'xinclude', 'reader', 'api', 'lint', 'schema']	[]

Directories in report

Directory
/src/libxml2/./codegen/
/src/libxml2/fuzz/../
/src/libxml2/./
/src/libxml2/fuzz/
/src/libxml2/./include/private/
/src/libxml2/