Submit libp2p to oss-fuzz
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 6.9k
- Forks
- 1.3k
- Avg merge
- 13d 21h
- Merged PRs (30d)
- 1
Description
go-libp2p probably gets enough usage that it would be valuable to have a background fuzz testing framework running against it.
if we have a docker image building a `go-fuzz` entrypoint to libp2p, then we can submit to google's oss-fuzz (https://github.com/google/oss-fuzz/tree/master/projects) and the google cloud will do much of the automation.
docs: https://google.github.io/oss-fuzz//getting-started/new-project-guide/go-lang/
Contributor guide
No contributing guide indexed for this repository
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
The issue names no repository files or tests. Start with the linked OSS-Fuzz Go new-project guide, then define the Docker image and go-fuzz entrypoint described here; done means libp2p is submitted as an OSS-Fuzz project with background fuzz testing running.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, go
- Domain
- networking, testing-qa
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100