Repository navigation
corpus: batch 4 — Java Spring CORS + Rust serde + C rand - #117
Merged
Merged
Conversation
Bench 18 → 21. Three more matcher slugs. - java-spring-cors-wildcard: @crossorigin(origins="*") + allowCredentials=true - rust-deserialize-from-str-untrusted: serde_json::from_str + bincode::deserialize - c-rand-for-security: rand() in a token-minting routine (security keywords required for matcher to fire — added in a doc comment) c-rand fixture split into token.c (vulnerable, security-flavoured) and dice.c (safe, no security keywords) because the matcher's require_content gates on those keywords AT FILE LEVEL. rust-serde issue includes rust-panic-on-untrusted in vulnSlugs — both matchers correctly fire on `from_str(...).unwrap()` and would otherwise count one as an FP. Whole-bench: recall 0.9730 → 0.9756, precision 1.0. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
13 of 15 tasks
noeljackson
added a commit
that referenced
this pull request
May 15, 2026
…#117) Bench 18 → 21. Three more matcher slugs. - java-spring-cors-wildcard: @crossorigin(origins="*") + allowCredentials=true - rust-deserialize-from-str-untrusted: serde_json::from_str + bincode::deserialize - c-rand-for-security: rand() in a token-minting routine (security keywords required for matcher to fire — added in a doc comment) c-rand fixture split into token.c (vulnerable, security-flavoured) and dice.c (safe, no security keywords) because the matcher's require_content gates on those keywords AT FILE LEVEL. rust-serde issue includes rust-panic-on-untrusted in vulnSlugs — both matchers correctly fire on `from_str(...).unwrap()` and would otherwise count one as an FP. Whole-bench: recall 0.9730 → 0.9756, precision 1.0. Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
noeljackson
added a commit
that referenced
this pull request
May 18, 2026
…#117) Bench 18 → 21. Three more matcher slugs. - java-spring-cors-wildcard: @crossorigin(origins="*") + allowCredentials=true - rust-deserialize-from-str-untrusted: serde_json::from_str + bincode::deserialize - c-rand-for-security: rand() in a token-minting routine (security keywords required for matcher to fire — added in a doc comment) c-rand fixture split into token.c (vulnerable, security-flavoured) and dice.c (safe, no security keywords) because the matcher's require_content gates on those keywords AT FILE LEVEL. rust-serde issue includes rust-panic-on-untrusted in vulnSlugs — both matchers correctly fire on `from_str(...).unwrap()` and would otherwise count one as an FP. Whole-bench: recall 0.9730 → 0.9756, precision 1.0.
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
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.
Toward #84. Bench 18 → 21. 3 new matcher slugs. Recall 0.9730 → 0.9756, precision 1.0.
🤖 Generated with Claude Code