-
Notifications
You must be signed in to change notification settings - Fork 2.3k
Issues: google/oss-fuzz
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.
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
Author
Label
Projects
Milestones
Assignee
Sort
Issues list
Failed to get component revisions - is this an intented behaviour?
#13145
opened Mar 18, 2025 by
Jarvx
Comments with LLM-generated fixes when issues are already verified and closed
#13142
opened Mar 17, 2025 by
evverx
Standalone Python Module for Querying OSS-Fuzz Project Details & Historical Results
#13139
opened Mar 17, 2025 by
1himan
Issues not reported - Minimized Testcase: Pending - even though it finished.
#13116
opened Mar 6, 2025 by
kasper93
QEMU: Some corpus backups being generated. No coverage reports generated at all
#13115
opened Mar 5, 2025 by
a1xndr
can pysource-codegen be integrated as fuzzing engine for python?
#13049
opened Feb 16, 2025 by
15r10nk
Bump Clang version is required due to a possible collision in profile data filenames
#13019
opened Feb 7, 2025 by
ligurio
base-builder image uses Ubuntu 20.04, new version with Ubuntu 24.04 needed for fuzzing expat
#13016
opened Feb 7, 2025 by
hartwork
Fix Broken Actions due to Removed
actions/upload-artifact@v3
#13011
opened Feb 6, 2025 by
Alexhuszagh
Non-zero return values from LLVMFuzzerTestOneInput should be discouraged
#12960
opened Jan 22, 2025 by
phi-go
Missing Introspector data on after successful Fuzz Introspector build
#12959
opened Jan 21, 2025 by
eaubin
[uriparser] 3 of 6 public corpus downloads fail with HTTP status 403 — please help!
#12948
opened Jan 17, 2025 by
hartwork
Previous Next
ProTip!
Add no:assignee to see everything that’s not assigned.