bytecodealliance / bytecodealliance/wasmtime

Consider integrating Fuzz Introspector into our continuous fuzzing setup

Open
#9,699 3 comments 0 reactions 0 assignees View on GitHub
enhancement fuzzing
Dominant language
Rust
Stars
18.6k
Forks
1.8k
Avg merge
1d 18h
Merged PRs (30d)
126

Description

#### Feature

[Fuzz Introspector](https://github.com/ossf/fuzz-introspector) helps to gain insights into the effectiveness of a fuzzing setup and to identify blockers that keep parts of the code base uncovered.

#### Benefit

Wasmtime is sufficiently complex that it's challenging to reason about the effectiveness of the various fuzzing harnesses we employ. That's the very problem Fuzz Introspector was created to help address.

#### Implementation

Rust support was [added to Fuzz Introspector](https://github.com/ossf/fuzz-introspector/pull/1818) very recently, so it's not yet fully documented. I think that PR contains sufficient bread crumbs to find the right path to integration with our OSS-Fuzz setup, though.

#### Alternatives

There might be alternative initiatives with similar goals that'd be more valuable to integrate. If so, I'm not aware of them.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.