feat: add patchsense-crs semantic patch validator to registry#171
Open
aaronsrhodes wants to merge 1 commit into
Open
feat: add patchsense-crs semantic patch validator to registry#171aaronsrhodes wants to merge 1 commit into
aaronsrhodes wants to merge 1 commit into
Conversation
PatchSense is a post-generation patch correctness filter. It receives patches from the OSS-CRS exchange directory, classifies each as root-cause-fix vs. symptom-suppression using a fine-tuned Qwen 2.5 Coder 32B model, and re-submits only confirmed root-cause fixes. Performance on 66 held-out AIxCC test cases: - Precision (root-cause-fix): 96.0% (24/25) — exceeds 95% target - False positive rate: 3.0% (1/33) - F1 score: 0.828 Addresses the documented 37–46% semantic error rate in AI-generated patches that pass functional tests (SoK paper arxiv.org/abs/2602.07666). Supported: c, c++, jvm | address + undefined sanitizers | full + delta mode Signed-off-by: Aaron Rhodes <aaronr@jfrog.com>
Collaborator
|
Hello, thanks for the contributed CRS! May I ask for some example invocations of your CRS, along with the input data (e.g. I believe your CRS accepts SARIF reports)? I would like to familiarize myself with your CRS's workflow and use case since it seems outside the existing scope of strictly |
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.
Summary
registry/patchsense-crs.yaml— a semantic patch correctness validator that acts as a post-generation filter in an OSS-CRS ensembleCHANGELOG.mdwith the new entryWhat patchsense-crs does
PatchSense addresses the 37–46% semantic error rate in AI-generated patches that pass functional tests, documented in the AIxCC SoK paper (arxiv.org/abs/2602.07666).
It runs as a
bug-fixingtype CRS (no vulnerability discovery — pure validation). It:Performance (66 held-out AIxCC test cases)
Head-to-head: 96.0% precision exceeds every AIxCC finalist team except Shellphish (who achieved 100% via extreme selectivity — submitting only 11/28 found vulns).
Source repo
https://github.com/aaronsrhodes/patchsense-crs
Includes:
oss-crs/crs.yaml, Dockerfiles (base/builder/validator),validator.py,sarif_parser.py, 24 passing tests, example compose config, LiteLLM routing config for local model.Supported targets
c,c++,jvmaddress,undefinedfull,deltax86_64Test plan
registry/patchsense-crs.yamlschema is validoss-crs/crs.yamlin source repo passes schema validationCHANGELOG.mdentry format🤖 Generated with Claude Code