DavidKorczynski
DavidKorczynski
The ordering in the calltree depends on the location at which each node is in the source code. This makes it convenient to keep a pattern that follows the source-code...
Add feature for displaying bugs in the calltree - i.e. bugs that have been found by a given fuzzer over time. This could be mixed with with https://osv.dev/ integration where...
Fuzz-introspector has issues with large projects on OSS-Fuzz and Git is an example of this. When running fuzz-introspector on Git there are two issues: 1) The initial compiling of fuzzers...
One of the project examples in the repository is dng_sdk (https://android.googlesource.com/platform/external/dng_sdk/+/refs/heads/master/) dng_sdk is a C++ library and the current reachability extraction is sub-optimal on this example. An example is that...
libFuzzer has the ability to prioritise fuzzing of certain functions. We should use the data from the reachability and coverage analysis to feed information back to the fuzzer about nice-to-analyse...
Add [CIFuzz](https://google.github.io/oss-fuzz/getting-started/continuous-integration/) workflow action to have fuzzers build and run on each PR. This is a service offered by OSS-Fuzz where Logback already runs. CIFuzz can help detect catch regressions...
This fuzzer loads an arbitrary model and runs a simple inference on it. This fuzzer will be picked up and run by OSS-Fuzz.
This adds fuzzing by way of [ClusterFuzzLite](https://google.github.io/clusterfuzzlite/), which is a GitHub action that will perform a short amount of fuzzing for new PRs. The goal is to use fuzzing to...
This is an effort to migrate fuzzers from OSS-Fuzz to upstream. I've added it such that it's also a unit test that is run by way of pytest. The reason...
Add [CIFuzz](https://google.github.io/oss-fuzz/getting-started/continuous-integration/) workflow action to have fuzzers build and run on each PR. This is a service offered by OSS-Fuzz, on which coveragepy already runs. CIFuzz can help detect catch...