Turn one parser, decoder, protocol entry point, file format, or public API into a repeatable fuzzing target your team can keep using.

You receive: • Buildable fuzz harness for the agreed entry point • AddressSanitizer and UndefinedBehaviorSanitizer configuration where supported • Small starter corpus and documented invocation • Crash deduplication and testcase minimization for observed failures • Root-cause note and regression test for one confirmed defect, when found • CI integration guidance and a concise handoff

Process:

Confirm the reachable input boundary and build environment

Build the smallest stable harness

Establish sanitizer-clean seed execution

Run a focused local campaign and triage unique failures

Minimize useful cases and document reproduction

Deliver the harness, corpus, findings, and verification commands

To begin, I need the source repository or archive, build instructions, the target entry point, expected input format, and any existing sample files. This is a bounded engineering sprint; it does not include production testing or access to third-party data.