Skip to content

Issues: google/oss-fuzz-gen

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

73 Open 42 Closed
73 Open 42 Closed
Author
Filter by author
Loading
Label
Filter by label
Loading
Use alt + click/return to exclude labels
or ⇧ + click/return for logical OR
Projects
Filter by project
Loading
Milestones
Filter by milestone
Loading
Assignee
Filter by who’s assigned
Sort
Sort by
Newest Oldest Most commented Least commented Recently updated Least recently updated Best match
Most reactions
👍 👎 😄 🎉 😕 ❤️ 🚀 👀

Issues list

Incorrect Benchmark Status on report's Index Page
#721 opened Nov 21, 2024 by DonggeLiu
@oliverchang
Pass new fuzz targets to docker containers at runtime infra
#698 opened Nov 6, 2024 by oliverchang
1
Use cached builds enhancement New feature or request
#682 opened Nov 1, 2024 by oliverchang
5 of 6 tasks
@DavidKorczynski @oliverchang
Refine triaging logic, improve web crash details and add better "TP/FP" indicator
#656 opened Sep 29, 2024 by DavidKorczynski
@DavidKorczynski @arthurscchan
1
JCC is not compatible with some projects.
#653 opened Sep 26, 2024 by DonggeLiu
Sanity check harnesses in the coverage reports and/or builds
#635 opened Sep 20, 2024 by DavidKorczynski
@DavidKorczynski
missing error logs for failed build
#625 opened Sep 18, 2024 by DavidKorczynski
Fix some cases where auto-identification of harness/sources provides incorrect information
#612 opened Sep 14, 2024 by DavidKorczynski
@DavidKorczynski
Add cloud runner coverage support for python
#608 opened Sep 14, 2024 by DavidKorczynski
@DavidKorczynski
Add line numbers to harness code in reports
#579 opened Sep 6, 2024 by DavidKorczynski
@DavidKorczynski
Generated target antipattern: misuse of ConsumeData prompt-engineering
#575 opened Sep 5, 2024 by oliverchang
5
Agent-enhancement
#558 opened Aug 22, 2024 by DonggeLiu
2
More robust and dynamic way to obtain fuzz target info
#525 opened Aug 2, 2024 by DonggeLiu
@DavidKorczynski
3
Reuse existing build containers when testing auto-generated harnesses
#499 opened Jul 19, 2024 by DavidKorczynski
@DavidKorczynski
"Project not in OSS-Fuzz (likely only contains a project.yaml file)" when generate a benchmark-yaml.
#498 opened Jul 19, 2024 by aT0ngMu
@DavidKorczynski
1
Logic for test-to-harness conversion
#494 opened Jul 17, 2024 by DavidKorczynski
@DavidKorczynski
2
Use LLMs to generate corpus
#482 opened Jul 14, 2024 by DavidKorczynski
@DavidKorczynski
1
Early results for vulnerability analysis and remediation for OSS-Fuzz bugs
#458 opened Jul 8, 2024 by inferno-chromium
6
Merge experimental/c-cpp with core
#450 opened Jul 8, 2024 by DavidKorczynski
@DavidKorczynski
1
Mitigate "finish_reason": "RECITATION" error in VertexAI queries. infra
#381 opened Jun 25, 2024 by DonggeLiu
2
Assert temperature in argparser
#366 opened Jun 21, 2024 by DonggeLiu
@DonggeLiu
Maximize overall coverage by showing overlapping benchmarks
#356 opened Jun 19, 2024 by DonggeLiu
3
Aggregate code coverage of all fuzz targets per benchmark
#355 opened Jun 19, 2024 by DonggeLiu
Automate Aggregation of Overall Coverage per project
#354 opened Jun 19, 2024 by DonggeLiu
@erfanio
Add C specific harness generation logic
#337 opened Jun 15, 2024 by DavidKorczynski
@DavidKorczynski
1
ProTip! Type g p on any issue or pull request to go back to the pull request listing page.