trailofbits / trailofbits/test-fuzz
What can be learned from `fuzzcheck-rs`?
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 208
- Forks
- 27
- Avg merge
- 9h 14m
- Merged PRs (30d)
- 9
Description
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the linked fuzzcheck-rs repository and the referenced Reddit discussion. The issue names no files, tests, entry points, or completion criteria, so clarify which ideas should be evaluated and what change or documented outcome would count as done.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- testing-qa
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100