Fuzz introspector
For issues and ideas: https://github.com/ossf/fuzz-introspector/issues
Report generation date: 2023-06-07

Project overview: croniter

High level conclusions

Reachability and coverage overview

Functions statically reachable by fuzzers
46.0%
22 / 48
Cyclomatic complexity statically reachable by fuzzers
47.0%
88 / 187
Runtime code coverage of functions
85.0%
41 / 48

Warning: The number of runtime covered functions are larger than the number of reachable functions. This means that Fuzz Introspector found there are more functions covered at runtime than what is considered reachable based on the static analysis. This is a limitation in the analysis as anything covered at runtime is by definition reachable by the fuzzers.
This is likely due to a limitation in the static analysis. In this case, the count of functions covered at runtime is the true value, which means this is what should be considered "achieved" by the fuzzer.

Use the project functions table below to query all functions that were not covered at runtime.

Fuzzer details

Fuzzer: fuzz_range

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 8 36.3%
gold [1:9] 0 0.0%
yellow [10:29] 0 0.0%
greenyellow [30:49] 0 0.0%
lawngreen 50+ 14 63.6%
All colors 22 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
6 8 ...fuzz_range.TestOneInput call site: 00008 .type
1 15 croniter.croniter_range call site: 00015 datetime.datetime.utcfromtimestamp
1 20 croniter.croniter_range call site: 00020 ic.get_current

Runtime coverage analysis

Covered functions
43
Functions that are reachable but not covered
13
Reachable functions
16
Percentage of reachable functions covered
18.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.
Warning: The number of covered functions are larger than the number of reachable functions. This means that there are more functions covered at runtime than are extracted using static analysis. This is likely a result of the static analysis component failing to extract the right call graph or the coverage runtime being compiled with sanitizers in code that the static analysis has not analysed. This can happen if lto/gold is not used in all places that coverage instrumentation is used.
Function name source code lines source lines hit percentage hit

Files reached

filename functions hit
/ 1
...fuzz_range 7
croniter 8

Fuzzer: fuzz_match

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

Fuzz blockers

The following nodes represent call sites where fuzz blockers occur.

Amount of callsites blocked Calltree index Parent function Callsite Largest blocked function
4 18 croniter.croniter._datetime_to_timestamp call site: 00018 time.time.replace
4 53 croniter.croniter._expand call site: 00053 .int
4 65 croniter.croniter._expand call site: 00065 .len
2 58 croniter.croniter._expand call site: 00058 .max
1 10 croniter.croniter.__init__ call site: 00010 hash_id.encode
1 13 croniter.croniter.__init__ call site: 00013 time.time
1 41 croniter.croniter._expand call site: 00041 .str
1 44 croniter.croniter._expand call site: 00044 .str

Runtime coverage analysis

Covered functions
43
Functions that are reachable but not covered
50
Reachable functions
61
Percentage of reachable functions covered
18.03%
NB: The sum of covered functions and functions that are reachable but not covered need not be equal to Reachable functions . This is because the reachability analysis is an approximation and thus at runtime some functions may be covered that are not included in the reachability analysis. This is a limitation of our static analysis capabilities.
Function name source code lines source lines hit percentage hit

Files reached

filename functions hit
/ 1
...fuzz_match 7
croniter 53

Fuzzer: fuzz_iter

Call tree

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

Call tree overview bitmap:

The distribution of callsites in terms of coloring is
Color Runtime hitcount Callsite count Percentage
red 0 36 27.9%
gold [1:9] 0 0.0%
yellow [10:29] 0 0.0%
greenyellow [30:49] 0 0.0%
lawngreen 50+ 93 72.0%
All colors 129 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
10 111 croniter.croniter._get_next call site: 00111 croniter.croniter._datetime_to_timestamp
8 78 croniter.croniter._datetime_to_timestamp call site: 00078 time.time.microseconds.replace
4 34 croniter.croniter._expand call site: 00034 .int
4 46 croniter.croniter._expand call site: 00046 .len
2 39 croniter.croniter._expand call site: 00039 .max
2 100 croniter.croniter._timestamp_to_datetime call site: 00100 dateutil.tz.tzutc
2 108 croniter.croniter._get_next call site: 00108 dtstarttime.utcoffset
1 22 croniter.croniter._expand call site: 00022 .str
1 25 croniter.croniter._expand call site: 00025 .str
1 70 croniter.croniter.__init__ call site: 00070 hash_id.encode
1 73 croniter.croniter.__init__ call site: 00073 time.time

Runtime coverage analysis

Covered functions
43
Functions that are reachable but not covered
58
Reachable functions
75
Percentage of reachable functions covered
22.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
/ 1
...fuzz_iter 10
croniter 66