Videos & Presentations
Short narrated walkthroughs of setting up OSS-CRS and running a CRS end to end, plus slides from public talks.
The videos follow one workflow: set up OSS-CRS, run the LibFuzzer bug-finding CRS against a target, inspect the seeds and proofs of vulnerability (POVs) it produces, and then pass those POVs to a Claude Code bug-fixing CRS that writes a patch. Watch them in order, or jump to the step you need.
Training videos
| # | Video | Length | What it covers |
|---|---|---|---|
| 1 | Set up OSS-CRS | 3:15 | oss-crs setup: routing LLM providers through a proxy (provider selection, API key and base URL env vars) and the cgroup v2 delegation step for CPU and memory isolation (Linux x86 only). |
| 2 | Set variables for the LibFuzzer CRS | 1:15 | Defining the compose file (CRS), the harness (HARNESS) and the target project (TARGET) for a bug-finding campaign. |
| 3 | Prepare the LibFuzzer CRS | 0:41 | oss-crs prepare: building the CRS base image and pre-caching tools so later phases don't rebuild. |
| 4 | Build a target for LibFuzzer | 1:42 | oss-crs build-target: compiling the target with sanitizers (ASan, UBSan, MSan) and coverage instrumentation, and linking it against the fuzzing harness. |
| 5 | Run the LibFuzzer CRS | 2:03 | oss-crs run: initializing the CRS, validating the configuration, preparing the run environment and starting the fuzzer with its sidecars. |
| 6 | LibFuzzer outputs: seeds and POVs | 2:13 | What seeds and proofs of vulnerability are, where they are stored under SUBMIT_DIR, and how to view them in the web UI dashboard. |
| 7 | Run a patching CRS | 4:44 | Passing LibFuzzer POVs to the Claude Code bug-fixing CRS with --pov-dir, using the LiteLLM proxy, and reviewing the generated patch. |
Slides
Related documentation
- Quick Start: the commands shown in these videos, step by step
- Setup Command: details of
oss-crs setup - LLM Providers: LiteLLM proxy configuration
- libCRS: how CRSs submit and fetch seeds, POVs and patches