Add OSS-Fuzz integration for 10 Go libraries: badger, gorilla/websocket, golang-jwt, opa, lego, crypto/ssh, testify, pgx, viper, semver#15627
Conversation
|
Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA). View this failed invocation of the CLA check for more information. For the most up to date status, view the checks section at the bottom of the pull request. |
|
canolgun-commits is integrating a new project, but the |
|
@googlebot I signed it! |
|
I have signed the Google CLA (canolgun@gmail.com). The CLA check at https://cla.developers.google.com/ shows signed. Please re-trigger the check. |
|
CLA should now be linked to GitHub username canolgun-commits. @googlebot please recheck. |
badger, gorilla/websocket, golang-jwt, opa, lego, crypto/ssh, testify, pgx, viper — 4 fuzz targets each with Dockerfile, build.sh, fuzz_test.go, and project.yaml. Sanitizers: address, memory Engine: libfuzzer (Go native fuzz)
DavidKorczynski
left a comment
There was a problem hiding this comment.
Please coordinate with the maintainers of these projects for approval and land the fuzzing harnesses in the upstream repositories. Each project should have its own PR with a clarification for why the given project is critical.
Adds OSS-Fuzz integration for 9 widely-used Go libraries:
Each project: 4 fuzz targets + Dockerfile + build.sh + project.yaml.
Sanitizers: address, memory. Engine: libfuzzer (Go native fuzz).
All fuzz targets verified with
go test -fuzz=. -fuzztime=30s.