High level conclusions

Fuzzers reach 95.96% of cyclomatic complexity.

Fuzzers reach 92.43% of all functions.

Fuzzers reach 91.63% code coverage.

Reachability and coverage overview

Functions statically reachable by fuzzers

232 / 251

Cyclomatic complexity statically reachable by fuzzers

1331 / 1387

Runtime code coverage of functions

230 / 251

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

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	0	0.0%
gold	[1:9]	0	0.0%
yellow	[10:29]	4	80.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	1	20.0%
All colors	5	100

Runtime coverage analysis

Covered functions

3

Functions that are reachable but not covered

2

Reachable functions

5

Percentage of reachable functions covered

60.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
apps/fuzzers/fuzzerIndexIO.c	1
h3lib/lib/h3Index.c	2

Fuzzer: fuzzerCompact

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	0	0.0%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	35	100.%
All colors	35	100

Runtime coverage analysis

Covered functions

18

Functions that are reachable but not covered

2

Reachable functions

20

Percentage of reachable functions covered

90.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
apps/fuzzers/fuzzerCompact.c	1
h3lib/lib/h3Index.c	9
h3lib/lib/baseCells.c	1
h3lib/lib/mathExtensions.c	1
h3lib/lib/iterators.c	6

Fuzzer: fuzzerDistances

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	0	0.0%
gold	[1:9]	0	0.0%
yellow	[10:29]	4	36.3%
greenyellow	[30:49]	1	9.09%
lawngreen	50+	6	54.5%
All colors	11	100

Runtime coverage analysis

Covered functions

4

Functions that are reachable but not covered

4

Reachable functions

8

Percentage of reachable functions covered

50.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
apps/fuzzers/fuzzerDistances.c	1
h3lib/lib/latLng.c	3

Fuzzer: fuzzerCellToLatLng

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	1	0.68%
gold	[1:9]	8	5.51%
yellow	[10:29]	9	6.20%
greenyellow	[30:49]	12	8.27%
lawngreen	50+	115	79.3%
All colors	145	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
1	71	_geoAzDistanceRads	call site: 00071	constrainLng

Runtime coverage analysis

Covered functions

39

Functions that are reachable but not covered

8

Reachable functions

47

Percentage of reachable functions covered

82.98%

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
apps/fuzzers/fuzzerCellToLatLng.c	1
h3lib/lib/h3Index.c	8
h3lib/lib/baseCells.c	1
h3lib/lib/coordijk.c	15
h3lib/lib/faceijk.c	8
h3lib/lib/vec2d.c	3
h3lib/lib/latLng.c	3

Fuzzer: fuzzerCellProperties

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	0	0.0%
gold	[1:9]	2	1.78%
yellow	[10:29]	7	6.25%
greenyellow	[30:49]	11	9.82%
lawngreen	50+	92	82.1%
All colors	112	100

Runtime coverage analysis

Covered functions

39

Functions that are reachable but not covered

3

Reachable functions

42

Percentage of reachable functions covered

92.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
apps/fuzzers/fuzzerCellProperties.c	1
h3lib/lib/h3Index.c	19
h3lib/lib/baseCells.c	1
h3lib/lib/coordijk.c	14
h3lib/lib/faceijk.c	4

Fuzzer: fuzzerInternalAlgos

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	5	2.43%
gold	[1:9]	0	0.0%
yellow	[10:29]	3	1.46%
greenyellow	[30:49]	3	1.46%
lawngreen	50+	194	94.6%
All colors	205	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
1	13	_h3Rotate60cw	call site: 00013	_h3Rotate60ccw
1	30	LLVMFuzzerTestOneInput	call site: 00030	initVertexGraph
1	131	_hex2dToGeo	call site: 00131	_posAngleRads
1	135	_geoAzDistanceRads	call site: 00135	constrainLng
1	200	_vertexGraphToLinkedGeo	call site: 00200	findNodeForEdge

Runtime coverage analysis

Covered functions

62

Functions that are reachable but not covered

11

Reachable functions

73

Percentage of reachable functions covered

84.93%

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
apps/fuzzers/fuzzerInternalAlgos.c	1
h3lib/lib/algos.c	4
h3lib/lib/coordijk.c	16
h3lib/lib/h3Index.c	9
h3lib/lib/baseCells.c	3
h3lib/lib/vertexGraph.c	9
h3lib/lib/faceijk.c	7
h3lib/lib/vec2d.c	3
h3lib/lib/latLng.c	5
h3lib/lib/linkedGeo.c	5

Fuzzer: fuzzerGridDisk

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	1	1.29%
gold	[1:9]	0	0.0%
yellow	[10:29]	2	2.59%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	74	96.1%
All colors	77	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
1	23	_h3Rotate60cw	call site: 00023	_h3Rotate60ccw

Runtime coverage analysis

Covered functions

26

Functions that are reachable but not covered

2

Reachable functions

28

Percentage of reachable functions covered

92.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
apps/fuzzers/fuzzerGridDisk.c	1
h3lib/lib/algos.c	12
h3lib/lib/latLng.c	1
h3lib/lib/mathExtensions.c	1
h3lib/lib/h3Index.c	6
h3lib/lib/baseCells.c	3
h3lib/lib/coordijk.c	2

Fuzzer: fuzzerCellsToLinkedMultiPolygon

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	1.45%
gold	[1:9]	1	0.48%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	1	0.48%
lawngreen	50+	201	97.5%
All colors	206	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
1	106	_hex2dToGeo	call site: 00106	_posAngleRads
1	110	_geoAzDistanceRads	call site: 00110	constrainLng
1	175	_vertexGraphToLinkedGeo	call site: 00175	findNodeForEdge

Runtime coverage analysis

Covered functions

68

Functions that are reachable but not covered

11

Reachable functions

79

Percentage of reachable functions covered

86.08%

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
apps/fuzzers/fuzzerCellsToLinkedMultiPolygon.c	1
h3lib/lib/algos.c	3
h3lib/lib/vertexGraph.c	9
h3lib/lib/h3Index.c	7
h3lib/lib/baseCells.c	1
h3lib/lib/coordijk.c	15
h3lib/lib/faceijk.c	7
h3lib/lib/vec2d.c	3
h3lib/lib/latLng.c	5
h3lib/lib/linkedGeo.c	11
h3lib/include/polygonAlgos.h	4
h3lib/lib/bbox.c	2

Fuzzer: fuzzerPolygonToCellsExperimental

Call tree

The calltree shows the control flow of the fuzzer. This is overlaid with coverage information to display how much of the potential code a fuzzer can reach is in fact covered at runtime. In the following there is a link to a detailed calltree visualisation as well as a bitmap showing a high-level view of the calltree. For further information about these topics please see the glossary for full calltree and calltree overview

Call tree overview bitmap:

The distribution of callsites in terms of coloring is

Color	Runtime hitcount	Callsite count	Percentage
red	0	11	3.33%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	2	0.60%
lawngreen	50+	317	96.0%
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
1	11	_iterInitPolygonCompact	call site: 00011	iterErrorPolygonCompact
1	13	_iterInitPolygonCompact	call site: 00013	iterErrorPolygonCompact
1	101	_geoAzDistanceRads	call site: 00101	constrainLng
1	114	_geoAzDistanceRads	call site: 00114	iterErrorPolygonCompact
1	173	_faceIjkToH3	call site: 00173	_h3Rotate60ccw
1	182	iterStepPolygonCompact	call site: 00182	iterErrorPolygonCompact
1	241	_faceIjkToCellBoundary	call site: 00241	iterErrorPolygonCompact
1	250	iterStepPolygonCompact	call site: 00250	iterErrorPolygonCompact
1	275	iterStepPolygonCompact	call site: 00275	iterErrorPolygonCompact
1	287	iterStepPolygonCompact	call site: 00287	iterErrorPolygonCompact
1	295	cellToCenterChild	call site: 00295	iterErrorPolygonCompact

Runtime coverage analysis

Covered functions

106

Functions that are reachable but not covered

11

Reachable functions

117

Percentage of reachable functions covered

90.6%

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
apps/fuzzers/fuzzerPolygonToCellsExperimental.c	3
h3lib/lib/polyfill.c	14
h3lib/lib/h3Index.c	17
h3lib/lib/polygon.c	7
h3lib/include/polygonAlgos.h	2
h3lib/lib/bbox.c	9
h3lib/lib/latLng.c	6
h3lib/lib/baseCells.c	4
h3lib/lib/coordijk.c	20
h3lib/lib/faceijk.c	11
h3lib/lib/vec2d.c	3
h3lib/lib/vec3d.c	3
h3lib/lib/mathExtensions.c	1
h3lib/lib/iterators.c	6

Fuzzer: fuzzerHierarchy

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	0	0.0%
gold	[1:9]	1	3.57%
yellow	[10:29]	1	3.57%
greenyellow	[30:49]	2	7.14%
lawngreen	50+	24	85.7%
All colors	28	100

Runtime coverage analysis

Covered functions

18

Functions that are reachable but not covered

1

Reachable functions

19

Percentage of reachable functions covered

94.74%

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
apps/fuzzers/fuzzerHierarchy.c	1
h3lib/lib/h3Index.c	9
h3lib/lib/baseCells.c	1
h3lib/lib/mathExtensions.c	1
h3lib/lib/iterators.c	6

Fuzzer: fuzzerPolygonToCells

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	25	8.89%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	256	91.1%
All colors	281	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
20	136	_faceIjkPentToCellBoundary	call site: 00136	_faceIjkToCellBoundary
2	265	gridDiskDistances	call site: 00265	getNumCells
1	83	_geoAzDistanceRads	call site: 00083	constrainLng
1	253	h3NeighborRotations	call site: 00253	_h3Rotate60ccw
1	271	_gridDiskDistancesInternal	call site: 00271	_gridDiskDistancesInternal

Runtime coverage analysis

Covered functions

81

Functions that are reachable but not covered

16

Reachable functions

97

Percentage of reachable functions covered

83.51%

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
apps/fuzzers/fuzzerPolygonToCells.c	3
h3lib/lib/algos.c	9
h3lib/lib/polygon.c	3
h3lib/include/polygonAlgos.h	2
h3lib/lib/bbox.c	5
h3lib/lib/h3Index.c	14
h3lib/lib/baseCells.c	5
h3lib/lib/coordijk.c	20
h3lib/lib/faceijk.c	11
h3lib/lib/vec2d.c	3
h3lib/lib/latLng.c	7
h3lib/lib/vec3d.c	3
h3lib/lib/mathExtensions.c	1

Fuzzer: fuzzerEdgeLength

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	2	1.21%
gold	[1:9]	0	0.0%
yellow	[10:29]	10	6.06%
greenyellow	[30:49]	12	7.27%
lawngreen	50+	141	85.4%
All colors	165	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
1	115	_hex2dToGeo	call site: 00115	_posAngleRads
1	119	_geoAzDistanceRads	call site: 00119	constrainLng

Runtime coverage analysis

Covered functions

48

Functions that are reachable but not covered

8

Reachable functions

56

Percentage of reachable functions covered

85.71%

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
apps/fuzzers/fuzzerEdgeLength.c	1
h3lib/lib/latLng.c	7
h3lib/lib/directedEdge.c	2
h3lib/lib/vertex.c	2
h3lib/lib/h3Index.c	7
h3lib/lib/baseCells.c	4
h3lib/lib/coordijk.c	15
h3lib/lib/faceijk.c	7
h3lib/lib/vec2d.c	3

Fuzzer: fuzzerLocalIj

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	0	0.0%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	159	100.%
All colors	159	100

Runtime coverage analysis

Covered functions

43

Functions that are reachable but not covered

3

Reachable functions

46

Percentage of reachable functions covered

93.48%

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
apps/fuzzers/fuzzerLocalIj.c	2
h3lib/lib/localij.c	8
h3lib/lib/baseCells.c	4
h3lib/lib/h3Index.c	7
h3lib/lib/coordijk.c	20
h3lib/include/mathExtensions.h	2

Fuzzer: fuzzerInternalCoordIjk

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	0	0.0%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	28	100.%
All colors	28	100

Runtime coverage analysis

Covered functions

7

Functions that are reachable but not covered

2

Reachable functions

9

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
apps/fuzzers/fuzzerInternalCoordIjk.c	1
h3lib/lib/coordijk.c	4
h3lib/include/mathExtensions.h	2

Fuzzer: fuzzerCellArea

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	1	0.60%
gold	[1:9]	0	0.0%
yellow	[10:29]	7	4.26%
greenyellow	[30:49]	2	1.21%
lawngreen	50+	154	93.9%
All colors	164	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
1	72	_geoAzDistanceRads	call site: 00072	constrainLng

Runtime coverage analysis

Covered functions

45

Functions that are reachable but not covered

9

Reachable functions

54

Percentage of reachable functions covered

83.33%

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
apps/fuzzers/fuzzerCellArea.c	1
h3lib/lib/latLng.c	9
h3lib/lib/h3Index.c	8
h3lib/lib/baseCells.c	1
h3lib/lib/coordijk.c	15
h3lib/lib/faceijk.c	8
h3lib/lib/vec2d.c	3

Fuzzer: fuzzerPolygonToCellsNoHoles

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	28	10.1%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	249	89.8%
All colors	277	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
20	133	_faceIjkPentToCellBoundary	call site: 00133	_faceIjkToCellBoundary
2	262	gridDiskDistances	call site: 00262	getNumCells
1	80	_geoAzDistanceRads	call site: 00080	constrainLng
1	166	bboxesFromGeoPolygon	call site: 00166	bboxFromGeoLoop
1	234	latLngToCell	call site: 00234	_getEdgeHexagons
1	250	h3NeighborRotations	call site: 00250	_h3Rotate60ccw
1	268	_gridDiskDistancesInternal	call site: 00268	_gridDiskDistancesInternal
1	275	pointInsideGeoLoop	call site: 00275	pointInsideGeoLoop

Runtime coverage analysis

Covered functions

80

Functions that are reachable but not covered

16

Reachable functions

96

Percentage of reachable functions covered

83.33%

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
apps/fuzzers/fuzzerPolygonToCellsNoHoles.c	2
h3lib/lib/algos.c	9
h3lib/lib/polygon.c	3
h3lib/include/polygonAlgos.h	2
h3lib/lib/bbox.c	5
h3lib/lib/h3Index.c	14
h3lib/lib/baseCells.c	5
h3lib/lib/coordijk.c	20
h3lib/lib/faceijk.c	11
h3lib/lib/vec2d.c	3
h3lib/lib/latLng.c	7
h3lib/lib/vec3d.c	3
h3lib/lib/mathExtensions.c	1

Fuzzer: fuzzerLatLngToCell

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	0	0.0%
gold	[1:9]	1	1.31%
yellow	[10:29]	3	3.94%
greenyellow	[30:49]	1	1.31%
lawngreen	50+	71	93.4%
All colors	76	100

Runtime coverage analysis

Covered functions

33

Functions that are reachable but not covered

7

Reachable functions

40

Percentage of reachable functions covered

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

Function name	source code lines	source lines hit	percentage hit

Files reached

filename	functions hit
apps/fuzzers/fuzzerLatLngToCell.c	1
h3lib/lib/h3Index.c	7
h3lib/lib/faceijk.c	3
h3lib/lib/vec3d.c	3
h3lib/lib/latLng.c	2
h3lib/lib/coordijk.c	13
h3lib/lib/baseCells.c	4

Fuzzer: fuzzerResolutions

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	0	0.0%
gold	[1:9]	1	10.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	9	90.0%
All colors	10	100

Runtime coverage analysis

Covered functions

10

Functions that are reachable but not covered

0

Reachable functions

10

Percentage of reachable functions covered

100.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
apps/fuzzers/fuzzerResolutions.c	1
h3lib/lib/latLng.c	5
h3lib/lib/mathExtensions.c	1
h3lib/lib/h3Index.c	2
h3lib/lib/baseCells.c	1

Fuzzer: fuzzerVertexes

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	20	9.95%
gold	[1:9]	1	0.49%
yellow	[10:29]	11	5.47%
greenyellow	[30:49]	1	0.49%
lawngreen	50+	168	83.5%
All colors	201	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
9	138	_faceIjkPentToCellBoundary	call site: 00138	_hex2dToGeo
7	183	_faceIjkToCellBoundary	call site: 00183	_hex2dToGeo
1	73	cellToVertex	call site: 00073	_rotate60ccw
1	84	h3NeighborRotations	call site: 00084	_h3Rotate60ccw
1	153	_hex2dToGeo	call site: 00153	_posAngleRads
1	157	_geoAzDistanceRads	call site: 00157	constrainLng

Runtime coverage analysis

Covered functions

57

Functions that are reachable but not covered

10

Reachable functions

67

Percentage of reachable functions covered

85.07%

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
apps/fuzzers/fuzzerVertexes.c	1
h3lib/lib/vertex.c	7
h3lib/lib/h3Index.c	15
h3lib/lib/baseCells.c	5
h3lib/lib/coordijk.c	16
h3lib/lib/faceijk.c	7
h3lib/lib/algos.c	2
h3lib/lib/vec2d.c	3
h3lib/lib/latLng.c	3

Fuzzer: fuzzerCellToChildPos

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	0	0.0%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	24	100.%
All colors	24	100

Runtime coverage analysis

Covered functions

11

Functions that are reachable but not covered

1

Reachable functions

12

Percentage of reachable functions covered

91.67%

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
apps/fuzzers/fuzzerCellToChildPos.c	1
h3lib/lib/h3Index.c	8
h3lib/lib/baseCells.c	1
h3lib/lib/mathExtensions.c	1

Fuzzer: fuzzerDirectedEdge

Call tree

The calltree shows the control flow of the fuzzer. This is overlaid with coverage information to display how much of the potential code a fuzzer can reach is in fact covered at runtime. In the following there is a link to a detailed calltree visualisation as well as a bitmap showing a high-level view of the calltree. For further information about these topics please see the glossary for full calltree and calltree overview

Call tree overview bitmap:

The distribution of callsites in terms of coloring is

Color	Runtime hitcount	Callsite count	Percentage
red	0	6	2.75%
gold	[1:9]	11	5.04%
yellow	[10:29]	20	9.17%
greenyellow	[30:49]	2	0.91%
lawngreen	50+	179	82.1%
All colors	218	100

Fuzz blockers

The following nodes represent call sites where fuzz blockers occur.

Amount of callsites blocked	Calltree index	Parent function	Callsite	Largest blocked function
2	38	gridDiskDistances	call site: 00038	getNumCells
1	23	_h3Rotate60cw	call site: 00023	_h3Rotate60ccw
1	44	_gridDiskDistancesInternal	call site: 00044	_gridDiskDistancesInternal
1	178	_hex2dToGeo	call site: 00178	_posAngleRads
1	182	_geoAzDistanceRads	call site: 00182	constrainLng

Runtime coverage analysis

Covered functions

68

Functions that are reachable but not covered

11

Reachable functions

79

Percentage of reachable functions covered

86.08%

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
apps/fuzzers/fuzzerDirectedEdge.c	1
h3lib/lib/directedEdge.c	8
h3lib/lib/h3Index.c	16
h3lib/lib/baseCells.c	5
h3lib/lib/algos.c	7
h3lib/lib/coordijk.c	16
h3lib/lib/latLng.c	4
h3lib/lib/mathExtensions.c	1
h3lib/lib/vertex.c	2
h3lib/lib/faceijk.c	7
h3lib/lib/vec2d.c	3

Fuzzer: fuzzerPolygonToCellsExperimentalNoHoles

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	15	4.60%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	3	0.92%
lawngreen	50+	308	94.4%
All colors	326	100

Fuzz blockers

The following nodes represent call sites where fuzz blockers occur.

Amount of callsites blocked	Calltree index	Parent function	Callsite	Largest blocked function
2	266	cellBoundaryCrossesGeoLoop	call site: 00266	cellBoundaryCrossesGeoLoop
1	8	_iterInitPolygonCompact	call site: 00008	iterErrorPolygonCompact
1	10	_iterInitPolygonCompact	call site: 00010	iterErrorPolygonCompact
1	13	bboxesFromGeoPolygon	call site: 00013	bboxFromGeoLoop
1	98	_geoAzDistanceRads	call site: 00098	constrainLng
1	111	_geoAzDistanceRads	call site: 00111	iterErrorPolygonCompact
1	117	pointInsideGeoLoop	call site: 00117	pointInsideGeoLoop
1	179	iterStepPolygonCompact	call site: 00179	iterErrorPolygonCompact
1	238	_faceIjkToCellBoundary	call site: 00238	iterErrorPolygonCompact
1	247	iterStepPolygonCompact	call site: 00247	iterErrorPolygonCompact
1	270	cellBoundaryCrossesPolygon	call site: 00270	cellBoundaryCrossesGeoLoop
1	272	iterStepPolygonCompact	call site: 00272	iterErrorPolygonCompact

Runtime coverage analysis

Covered functions

105

Functions that are reachable but not covered

11

Reachable functions

116

Percentage of reachable functions covered

90.52%

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
apps/fuzzers/fuzzerPolygonToCellsExperimentalNoHoles.c	2
h3lib/lib/polyfill.c	14
h3lib/lib/h3Index.c	17
h3lib/lib/polygon.c	7
h3lib/include/polygonAlgos.h	2
h3lib/lib/bbox.c	9
h3lib/lib/latLng.c	6
h3lib/lib/baseCells.c	4
h3lib/lib/coordijk.c	20
h3lib/lib/faceijk.c	11
h3lib/lib/vec2d.c	3
h3lib/lib/vec3d.c	3
h3lib/lib/mathExtensions.c	1
h3lib/lib/iterators.c	6

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

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

Functions statically reachable by fuzzers

232 / 251

Cyclomatic complexity statically reachable by fuzzers

1331 / 1387

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.

apps/fuzzers/fuzzerIndexIO.c

Dictionary

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

apps/fuzzers/fuzzerCompact.c

Dictionary

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

apps/fuzzers/fuzzerDistances.c

Dictionary

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

apps/fuzzers/fuzzerCellToLatLng.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=['_geoAzDistanceRads']

apps/fuzzers/fuzzerCellProperties.c

Dictionary

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

apps/fuzzers/fuzzerInternalAlgos.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=['_h3Rotate60cw', 'LLVMFuzzerTestOneInput', '_hex2dToGeo', '_geoAzDistanceRads', '_vertexGraphToLinkedGeo']

apps/fuzzers/fuzzerGridDisk.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=['_h3Rotate60cw']

apps/fuzzers/fuzzerCellsToLinkedMultiPolygon.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=['_hex2dToGeo', '_geoAzDistanceRads', '_vertexGraphToLinkedGeo']

apps/fuzzers/fuzzerPolygonToCellsExperimental.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=['_iterInitPolygonCompact', '_geoAzDistanceRads', '_faceIjkToH3', 'iterStepPolygonCompact', '_faceIjkToCellBoundary']

apps/fuzzers/fuzzerHierarchy.c

Dictionary

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

apps/fuzzers/fuzzerPolygonToCells.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=['_faceIjkPentToCellBoundary', 'gridDiskDistances', '_geoAzDistanceRads', 'h3NeighborRotations', '_gridDiskDistancesInternal']

apps/fuzzers/fuzzerEdgeLength.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=['_hex2dToGeo', '_geoAzDistanceRads']

apps/fuzzers/fuzzerLocalIj.c

Dictionary

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

apps/fuzzers/fuzzerInternalCoordIjk.c

Dictionary

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

apps/fuzzers/fuzzerCellArea.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=['_geoAzDistanceRads']

apps/fuzzers/fuzzerPolygonToCellsNoHoles.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=['_faceIjkPentToCellBoundary', 'gridDiskDistances', '_geoAzDistanceRads', 'bboxesFromGeoPolygon', 'latLngToCell', 'h3NeighborRotations', '_gridDiskDistancesInternal', 'pointInsideGeoLoop']

apps/fuzzers/fuzzerLatLngToCell.c

Dictionary

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

apps/fuzzers/fuzzerResolutions.c

Dictionary

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

apps/fuzzers/fuzzerVertexes.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=['_faceIjkPentToCellBoundary', '_faceIjkToCellBoundary', 'cellToVertex', 'h3NeighborRotations', '_hex2dToGeo', '_geoAzDistanceRads']

apps/fuzzers/fuzzerCellToChildPos.c

Dictionary

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

apps/fuzzers/fuzzerDirectedEdge.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=['gridDiskDistances', '_h3Rotate60cw', '_gridDiskDistancesInternal', '_hex2dToGeo', '_geoAzDistanceRads']

apps/fuzzers/fuzzerPolygonToCellsExperimentalNoHoles.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=['cellBoundaryCrossesGeoLoop', '_iterInitPolygonCompact', 'bboxesFromGeoPolygon', '_geoAzDistanceRads', 'pointInsideGeoLoop', 'iterStepPolygonCompact', '_faceIjkToCellBoundary']

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
_geoAzDistanceRads	50	26	52.0%	['fuzzerPolygonToCells', 'fuzzerPolygonToCellsNoHoles', 'fuzzerCellToLatLng', 'fuzzerDirectedEdge', 'fuzzerVertexes', 'fuzzerCellArea', 'fuzzerPolygonToCellsExperimental', 'fuzzerInternalAlgos', 'fuzzerEdgeLength', 'fuzzerCellsToLinkedMultiPolygon', 'fuzzerPolygonToCellsExperimentalNoHoles']

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/h3/src/h3lib/lib/h3Index.c	['fuzzerIndexIO', 'fuzzerCompact', 'fuzzerCellToLatLng', 'fuzzerCellProperties', 'fuzzerInternalAlgos', 'fuzzerGridDisk', 'fuzzerCellsToLinkedMultiPolygon', 'fuzzerPolygonToCellsExperimental', 'fuzzerHierarchy', 'fuzzerPolygonToCells', 'fuzzerEdgeLength', 'fuzzerLocalIj', 'fuzzerCellArea', 'fuzzerPolygonToCellsNoHoles', 'fuzzerLatLngToCell', 'fuzzerResolutions', 'fuzzerVertexes', 'fuzzerCellToChildPos', 'fuzzerDirectedEdge', 'fuzzerPolygonToCellsExperimentalNoHoles']	['fuzzerIndexIO', 'fuzzerCompact', 'fuzzerCellToLatLng', 'fuzzerCellProperties', 'fuzzerInternalAlgos', 'fuzzerGridDisk', 'fuzzerCellsToLinkedMultiPolygon', 'fuzzerPolygonToCellsExperimental', 'fuzzerHierarchy', 'fuzzerPolygonToCells', 'fuzzerEdgeLength', 'fuzzerLocalIj', 'fuzzerCellArea', 'fuzzerPolygonToCellsNoHoles', 'fuzzerLatLngToCell', 'fuzzerResolutions', 'fuzzerVertexes', 'fuzzerCellToChildPos', 'fuzzerDirectedEdge', 'fuzzerPolygonToCellsExperimentalNoHoles']
/src/h3/src/apps/fuzzers/fuzzerInternalAlgos.c	['fuzzerInternalAlgos']	['fuzzerInternalAlgos']
/src/h3/src/apps/fuzzers/fuzzerLatLngToCell.c	['fuzzerLatLngToCell']	['fuzzerLatLngToCell']
/src/h3/src/h3lib/lib/latLng.c	['fuzzerDistances', 'fuzzerCellToLatLng', 'fuzzerInternalAlgos', 'fuzzerGridDisk', 'fuzzerCellsToLinkedMultiPolygon', 'fuzzerPolygonToCellsExperimental', 'fuzzerPolygonToCells', 'fuzzerEdgeLength', 'fuzzerCellArea', 'fuzzerPolygonToCellsNoHoles', 'fuzzerLatLngToCell', 'fuzzerResolutions', 'fuzzerVertexes', 'fuzzerDirectedEdge', 'fuzzerPolygonToCellsExperimentalNoHoles']	['fuzzerDistances', 'fuzzerCellToLatLng', 'fuzzerInternalAlgos', 'fuzzerGridDisk', 'fuzzerCellsToLinkedMultiPolygon', 'fuzzerPolygonToCellsExperimental', 'fuzzerPolygonToCells', 'fuzzerEdgeLength', 'fuzzerCellArea', 'fuzzerPolygonToCellsNoHoles', 'fuzzerLatLngToCell', 'fuzzerResolutions', 'fuzzerVertexes', 'fuzzerDirectedEdge', 'fuzzerPolygonToCellsExperimentalNoHoles']
/src/h3/src/apps/fuzzers/fuzzerLocalIj.c	['fuzzerLocalIj']	['fuzzerLocalIj']
/src/h3/src/h3lib/lib/iterators.c	['fuzzerCompact', 'fuzzerPolygonToCellsExperimental', 'fuzzerHierarchy', 'fuzzerPolygonToCellsExperimentalNoHoles']	['fuzzerCompact', 'fuzzerPolygonToCellsExperimental', 'fuzzerHierarchy', 'fuzzerPolygonToCellsExperimentalNoHoles']
/src/h3/src/h3lib/lib/localij.c	['fuzzerLocalIj']	['fuzzerLocalIj']
/src/h3/src/apps/fuzzers/fuzzerHierarchy.c	['fuzzerHierarchy']	['fuzzerHierarchy']
/src/h3/src/apps/fuzzers/fuzzerPolygonToCells.c	['fuzzerPolygonToCells']	['fuzzerPolygonToCells']
/src/h3/src/apps/fuzzers/fuzzerCompact.c	['fuzzerCompact']	['fuzzerCompact']
/src/h3/src/apps/fuzzers/fuzzerInternalCoordIjk.c	['fuzzerInternalCoordIjk']	['fuzzerInternalCoordIjk']
/src/h3/src/apps/fuzzers/fuzzerCellsToLinkedMultiPolygon.c	['fuzzerCellsToLinkedMultiPolygon']	['fuzzerCellsToLinkedMultiPolygon']
/src/h3/src/apps/fuzzers/fuzzerPolygonToCellsExperimentalNoHoles.c	['fuzzerPolygonToCellsExperimentalNoHoles']	['fuzzerPolygonToCellsExperimentalNoHoles']
/src/h3/src/h3lib/lib/bbox.c	['fuzzerCellsToLinkedMultiPolygon', 'fuzzerPolygonToCellsExperimental', 'fuzzerPolygonToCells', 'fuzzerPolygonToCellsNoHoles', 'fuzzerPolygonToCellsExperimentalNoHoles']	['fuzzerCellsToLinkedMultiPolygon', 'fuzzerPolygonToCellsExperimental', 'fuzzerPolygonToCells', 'fuzzerPolygonToCellsNoHoles', 'fuzzerPolygonToCellsExperimentalNoHoles']
/src/h3/src/apps/fuzzers/fuzzerPolygonToCellsNoHoles.c	['fuzzerPolygonToCellsNoHoles']	['fuzzerPolygonToCellsNoHoles']
/src/h3/src/apps/fuzzers/fuzzerCellToLatLng.c	['fuzzerCellToLatLng']	['fuzzerCellToLatLng']
/src/h3/src/h3lib/include/polygonAlgos.h	['fuzzerCellsToLinkedMultiPolygon', 'fuzzerPolygonToCellsExperimental', 'fuzzerPolygonToCells', 'fuzzerPolygonToCellsNoHoles', 'fuzzerPolygonToCellsExperimentalNoHoles']	['fuzzerCellsToLinkedMultiPolygon', 'fuzzerPolygonToCellsExperimental', 'fuzzerPolygonToCells', 'fuzzerPolygonToCellsNoHoles', 'fuzzerPolygonToCellsExperimentalNoHoles']
/src/h3/src/h3lib/lib/vec2d.c	['fuzzerCellToLatLng', 'fuzzerInternalAlgos', 'fuzzerCellsToLinkedMultiPolygon', 'fuzzerPolygonToCellsExperimental', 'fuzzerPolygonToCells', 'fuzzerEdgeLength', 'fuzzerCellArea', 'fuzzerPolygonToCellsNoHoles', 'fuzzerVertexes', 'fuzzerDirectedEdge', 'fuzzerPolygonToCellsExperimentalNoHoles']	['fuzzerCellToLatLng', 'fuzzerInternalAlgos', 'fuzzerCellsToLinkedMultiPolygon', 'fuzzerPolygonToCellsExperimental', 'fuzzerPolygonToCells', 'fuzzerEdgeLength', 'fuzzerCellArea', 'fuzzerPolygonToCellsNoHoles', 'fuzzerVertexes', 'fuzzerDirectedEdge', 'fuzzerPolygonToCellsExperimentalNoHoles']
/src/h3/src/h3lib/lib/vec3d.c	['fuzzerPolygonToCellsExperimental', 'fuzzerPolygonToCells', 'fuzzerPolygonToCellsNoHoles', 'fuzzerLatLngToCell', 'fuzzerPolygonToCellsExperimentalNoHoles']	['fuzzerPolygonToCellsExperimental', 'fuzzerPolygonToCells', 'fuzzerPolygonToCellsNoHoles', 'fuzzerLatLngToCell', 'fuzzerPolygonToCellsExperimentalNoHoles']
/src/h3/src/apps/fuzzers/fuzzerCellProperties.c	['fuzzerCellProperties']	['fuzzerCellProperties']
/src/h3/src/apps/fuzzers/fuzzerEdgeLength.c	['fuzzerEdgeLength']	['fuzzerEdgeLength']
/src/h3/src/apps/fuzzers/fuzzerResolutions.c	['fuzzerResolutions']	['fuzzerResolutions']
/src/h3/src/h3lib/lib/baseCells.c	['fuzzerCompact', 'fuzzerCellToLatLng', 'fuzzerCellProperties', 'fuzzerInternalAlgos', 'fuzzerGridDisk', 'fuzzerCellsToLinkedMultiPolygon', 'fuzzerPolygonToCellsExperimental', 'fuzzerHierarchy', 'fuzzerPolygonToCells', 'fuzzerEdgeLength', 'fuzzerLocalIj', 'fuzzerCellArea', 'fuzzerPolygonToCellsNoHoles', 'fuzzerLatLngToCell', 'fuzzerResolutions', 'fuzzerVertexes', 'fuzzerCellToChildPos', 'fuzzerDirectedEdge', 'fuzzerPolygonToCellsExperimentalNoHoles']	['fuzzerCompact', 'fuzzerCellToLatLng', 'fuzzerCellProperties', 'fuzzerInternalAlgos', 'fuzzerGridDisk', 'fuzzerCellsToLinkedMultiPolygon', 'fuzzerPolygonToCellsExperimental', 'fuzzerHierarchy', 'fuzzerPolygonToCells', 'fuzzerEdgeLength', 'fuzzerLocalIj', 'fuzzerCellArea', 'fuzzerPolygonToCellsNoHoles', 'fuzzerLatLngToCell', 'fuzzerResolutions', 'fuzzerVertexes', 'fuzzerCellToChildPos', 'fuzzerDirectedEdge', 'fuzzerPolygonToCellsExperimentalNoHoles']
/src/h3/src/apps/fuzzers/fuzzerDirectedEdge.c	['fuzzerDirectedEdge']	['fuzzerDirectedEdge']
/src/h3/src/h3lib/lib/polygon.c	['fuzzerPolygonToCellsExperimental', 'fuzzerPolygonToCells', 'fuzzerPolygonToCellsNoHoles', 'fuzzerPolygonToCellsExperimentalNoHoles']	['fuzzerPolygonToCellsExperimental', 'fuzzerPolygonToCells', 'fuzzerPolygonToCellsNoHoles', 'fuzzerPolygonToCellsExperimentalNoHoles']
/src/h3/src/h3lib/lib/linkedGeo.c	['fuzzerInternalAlgos', 'fuzzerCellsToLinkedMultiPolygon']	['fuzzerInternalAlgos', 'fuzzerCellsToLinkedMultiPolygon']
/src/h3/src/apps/fuzzers/fuzzerGridDisk.c	['fuzzerGridDisk']	['fuzzerGridDisk']
/src/h3/src/h3lib/include/mathExtensions.h	['fuzzerLocalIj', 'fuzzerInternalCoordIjk']	['fuzzerLocalIj', 'fuzzerInternalCoordIjk']
/src/h3/src/h3lib/lib/polyfill.c	['fuzzerPolygonToCellsExperimental', 'fuzzerPolygonToCellsExperimentalNoHoles']	['fuzzerPolygonToCellsExperimental', 'fuzzerPolygonToCellsExperimentalNoHoles']
/src/h3/src/h3lib/lib/coordijk.c	['fuzzerCellToLatLng', 'fuzzerCellProperties', 'fuzzerInternalAlgos', 'fuzzerGridDisk', 'fuzzerCellsToLinkedMultiPolygon', 'fuzzerPolygonToCellsExperimental', 'fuzzerPolygonToCells', 'fuzzerEdgeLength', 'fuzzerLocalIj', 'fuzzerInternalCoordIjk', 'fuzzerCellArea', 'fuzzerPolygonToCellsNoHoles', 'fuzzerLatLngToCell', 'fuzzerVertexes', 'fuzzerDirectedEdge', 'fuzzerPolygonToCellsExperimentalNoHoles']	['fuzzerCellToLatLng', 'fuzzerCellProperties', 'fuzzerInternalAlgos', 'fuzzerGridDisk', 'fuzzerCellsToLinkedMultiPolygon', 'fuzzerPolygonToCellsExperimental', 'fuzzerPolygonToCells', 'fuzzerEdgeLength', 'fuzzerLocalIj', 'fuzzerInternalCoordIjk', 'fuzzerCellArea', 'fuzzerPolygonToCellsNoHoles', 'fuzzerLatLngToCell', 'fuzzerVertexes', 'fuzzerDirectedEdge', 'fuzzerPolygonToCellsExperimentalNoHoles']
/src/h3/src/apps/fuzzers/fuzzerIndexIO.c	['fuzzerIndexIO']	['fuzzerIndexIO']
/src/h3/src/h3lib/lib/vertex.c	['fuzzerEdgeLength', 'fuzzerVertexes', 'fuzzerDirectedEdge']	['fuzzerEdgeLength', 'fuzzerVertexes', 'fuzzerDirectedEdge']
/src/h3/src/apps/fuzzers/fuzzerPolygonToCellsExperimental.c	['fuzzerPolygonToCellsExperimental']	['fuzzerPolygonToCellsExperimental']
/src/h3/src/apps/fuzzers/fuzzerCellArea.c	['fuzzerCellArea']	['fuzzerCellArea']
/src/h3/src/h3lib/lib/vertexGraph.c	['fuzzerInternalAlgos', 'fuzzerCellsToLinkedMultiPolygon']	['fuzzerInternalAlgos', 'fuzzerCellsToLinkedMultiPolygon']
/src/h3/src/apps/fuzzers/fuzzerVertexes.c	['fuzzerVertexes']	['fuzzerVertexes']
/src/h3/src/apps/fuzzers/fuzzerCellToChildPos.c	['fuzzerCellToChildPos']	['fuzzerCellToChildPos']
/src/h3/src/h3lib/lib/algos.c	['fuzzerInternalAlgos', 'fuzzerGridDisk', 'fuzzerCellsToLinkedMultiPolygon', 'fuzzerPolygonToCells', 'fuzzerPolygonToCellsNoHoles', 'fuzzerVertexes', 'fuzzerDirectedEdge']	['fuzzerInternalAlgos', 'fuzzerGridDisk', 'fuzzerCellsToLinkedMultiPolygon', 'fuzzerPolygonToCells', 'fuzzerPolygonToCellsNoHoles', 'fuzzerVertexes', 'fuzzerDirectedEdge']
/src/h3/src/h3lib/lib/directedEdge.c	['fuzzerEdgeLength', 'fuzzerDirectedEdge']	['fuzzerEdgeLength', 'fuzzerDirectedEdge']
/src/h3/src/apps/fuzzers/fuzzerDistances.c	['fuzzerDistances']	['fuzzerDistances']
/src/h3/src/h3lib/lib/faceijk.c	['fuzzerCellToLatLng', 'fuzzerCellProperties', 'fuzzerInternalAlgos', 'fuzzerCellsToLinkedMultiPolygon', 'fuzzerPolygonToCellsExperimental', 'fuzzerPolygonToCells', 'fuzzerEdgeLength', 'fuzzerCellArea', 'fuzzerPolygonToCellsNoHoles', 'fuzzerLatLngToCell', 'fuzzerVertexes', 'fuzzerDirectedEdge', 'fuzzerPolygonToCellsExperimentalNoHoles']	['fuzzerCellToLatLng', 'fuzzerCellProperties', 'fuzzerInternalAlgos', 'fuzzerCellsToLinkedMultiPolygon', 'fuzzerPolygonToCellsExperimental', 'fuzzerPolygonToCells', 'fuzzerEdgeLength', 'fuzzerCellArea', 'fuzzerPolygonToCellsNoHoles', 'fuzzerLatLngToCell', 'fuzzerVertexes', 'fuzzerDirectedEdge', 'fuzzerPolygonToCellsExperimentalNoHoles']
/src/h3/src/h3lib/lib/mathExtensions.c	['fuzzerCompact', 'fuzzerGridDisk', 'fuzzerPolygonToCellsExperimental', 'fuzzerHierarchy', 'fuzzerPolygonToCells', 'fuzzerPolygonToCellsNoHoles', 'fuzzerResolutions', 'fuzzerCellToChildPos', 'fuzzerDirectedEdge', 'fuzzerPolygonToCellsExperimentalNoHoles']	['fuzzerCompact', 'fuzzerGridDisk', 'fuzzerPolygonToCellsExperimental', 'fuzzerHierarchy', 'fuzzerResolutions', 'fuzzerCellToChildPos', 'fuzzerPolygonToCellsExperimentalNoHoles']

Directories in report

Directory
/src/h3/src/apps/fuzzers/
/src/h3/src/h3lib/include/
/src/h3/src/h3lib/lib/