How does the precision-recall tradeoff in Gemini 1.5 Pro with an 8M context window compare to Llama3-70B with

Abstract

Abstract: Considerable delays often exist between the discovery of a vulnerability and the issue of a patch. One way to mitigate this window of vulnerability is to use a configuration workaround, which prevents the vulnerable code from being executed at the cost of some lost functionality – but only if one is available. Since program configurations are not specifically designed to mitigate software vulnerabilities, we find that they only cover 25.2\% of vulnerabilities. To minimize patch delay vulnerabilities and address the limitations of configuration workarounds, we propose Security Workarounds for

Research Question

How does the precision-recall tradeoff in Gemini 1.5 Pro with an 8M context window compare to Llama3-70B with retrieval augmentation on the CodeXGLUE security subset when classifying vulnerabilities across 5+ files?

Verification Level

Descriptive public verification status only; aggregate claim counts are public, but individual claim records are not exposed here.

Quality Tier

Descriptive public triage only; this tier does not alter current publication or DOI behavior.

Quality Dimensions

Automated triage signals derived from public fields; not human peer review or independent validation.

Correction Record

Public corrections are additive records. Current status does not claim the synthesis is error-free.

Provenance