Open
Conversation
|
0ai-Cyberviser is integrating a new project: |
Author
|
@copilot Copilot said: PR #63 can't be auto-merged because it'sPR #63 can't be auto-merged because it's still in draft state. You'll need to take two manual steps, then I can handle the rest: Step 1: Merge PR #63 (manual — requires your action)
This will land the Dockerfile and build.sh fixes onto the same branch that feeds google/oss-fuzz#15315. Step 2 (after merge): Update #15315 descriptionOnce #63 is merged, the
|
Author
|
@copilot Body: Adds Hancock (AI-powered cybersecurity agent) to OSS-Fuzz with 8 Atheris-based Python fuzz targets + seed corpora. Build verification python3 infra/helper.py build_image hancock |
0ai-Cyberviser
force-pushed
the
add-hancock-project
branch
from
762cdc1 to
785ca6d
Compare
Author
|
Local build + fuzz run verified successfully: ┌──(oai㉿0ai)-[~] 2. Build the Docker imagepython3 infra/helper.py build_image hancock 3. Build the fuzzerspython3 infra/helper.py build_fuzzers hancock 4. Run at least ONE fuzzer (recommend fuzz_nvd_parser as it's simple and representative)python3 infra/helper.py run_fuzzer hancock fuzz_nvd_parser -- -max_total_time=60
|
This was referenced Apr 15, 2026
|
Superseded by #15380. I pushed the same Hancock integration from a writable cyberviser/oss-fuzz fork and refreshed the project metadata and source URL to the current upstream repository location: https://github.com/cyberviser/Hancock. Please use #15380 for review going forward. Ignore the previous malformed shell-escaped comment. |
|
The original head branch has now been updated in place. The Hancock OSS-Fuzz project metadata and clone URL now point to the current upstream repository: https://github.com/cyberviser/Hancock. Please treat this PR as the active review target; the temporary replacement PR #15380 has been closed. |
|
The original head branch has been updated in place with the Hancock metadata/source URL refresh and this PR is now the active review target again. Current blocker appears to be maintainer approval for the fork-triggered pull_request workflows: |
cyberviser
approved these changes
Apr 18, 2026
cyberviser
approved these changes
Apr 18, 2026
cyberviser
approved these changes
Apr 18, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds Hancock (AI cybersecurity agent) to OSS-Fuzz with Atheris-based Python fuzz targets and seed corpora.
This integration is intentionally narrow:
projects/hancock/Dockerfileprojects/hancock/build.shprojects/hancock/project.yamlThe build compiles every
fuzz_*.pytarget present in the upstream Hancock repository and packages matching seed corpora fromfuzz/corpus/<name>/when available.Upstream fuzz targets + corpora: https://github.com/0ai-Cyberviser/Hancock/tree/main/fuzz
Supersedes the broader exploratory PRs
#15234and#15248by limiting the change to the Hancock project integration only.CIFuzz workflow is already enabled upstream.
Submitting for OSS-Fuzz Initial Integration reward (up to $5,000).