mlsanityData to 7 Oct 2026

Detecting False Alarms from Automatic Static Analysis Tools: How Far are We?

arXiv 2202.05982 ↗First posted 12 Feb 2022cs.SEcited by 16

Not on the map. Why?

Abstract (arXiv)

Automatic static analysis tools (ASATs), such as Findbugs, have a high false alarm rate. The large number of false alarms produced poses a barrier to adoption. Researchers have proposed the use of machine learning to prune false alarms and present only actionable warnings to developers. The state-of-the-art study has identified a set of "Golden Features" based on metrics computed over the characteristics and history of the file, code, and warning. Recent studies show that machine learning using these features is extremely effective and that they achieve almost perfect performance. We perform a detailed analysis to better understand the strong performance of the "Golden Features". We found that several studies used an experimental procedure that results in data leakage and data duplication, which are subtle issues with significant implications. Firstly, the ground-truth labels have leaked into features that measure the proportion of actionable warnings in a given context. Secondly, many warnings in the testing dataset appear in the training dataset. Next, we demonstrate limitations in the warning oracle that determines the ground-truth labels, a heuristic comparing warnings in a given revision to a reference revision in the future. We show the choice of reference revision influences the warning distribution. Moreover, the heuristic produces labels that do not agree with human oracles. Hence, the strong performance of these techniques previously seen is overoptimistic of their true performance if adopted in practice. Our results convey several lessons and provide guidelines for evaluating false alarm detectors.

Key facts. Cited by 16 papers in the map (data through 7 Oct 2026). First posted on arXiv 12 Feb 2022.

Builds on

No reference list yet.

Built on by

Cited by year (2026 to 7 Oct)

Citing papers per year: 2022: 1; 2023: 1; 2024: 6; 2025: 3; 2026: 5.

16 papers.

Sort:

By area:

  1. 2024Can LLMs Replace Manual Annotation of Software Engineering Artifacts?cited by 40
  2. 2024Comparison of Static Application Security Testing Tools and Large Language Models for Repo-level Vulnerability Detectioncited by 18
  3. 2024Black-Box Adversarial Attacks on LLM-Based Code Completioncited by 13
  4. 2025SecureVibeBench: Benchmarking Secure Vibe Coding of AI Agents via Reconstructing Vulnerability-Introducing Scenarioscited by 11
  5. 2026Sifting the Noise: A Comparative Study of LLM Agents in Vulnerability False Positive Filteringcited by 5
  6. 2025XOXO: Stealthy Cross-Origin Context Poisoning Attacks against AI Coding Assistantscited by 4
  7. 2024Can LLM Prompting Serve as a Proxy for Static Analysis in Vulnerability Detectioncited by 3
  8. 2024REDO: Execution-Free Runtime Error Detection for COding Agentscited by 2
  9. 2022How to Find Actionable Static Analysis Warnings: A Case Study with FindBugscited by 1
  10. 2024Is Hyper-Parameter Optimization Different for Software Analytics?cited by 1
  11. 2026Argus: Reorchestrating Static Analysis via a Multi-Agent Ensemble for Full-Chain Security Vulnerability Detectioncited by 1
  12. 2023Less, but Stronger: On the Value of Strong Heuristics in Semi-supervised Learning for Software Analyticscited by 0
4 more
  1. 2025Argus: A Multi-Agent Sensitive Information Leakage Detection Framework Based on Hierarchical Reference Relationshipscited by 0
  2. 2026Deep Learning-based Binary Analysis for Vulnerability Detection in x86-64 Machine Codecited by 0
  3. 2026Beyond Reproducibility: Towards Security-Aware Evaluation of Research Artifactscited by 0
  4. 2026Is Model Instability just Noise to be Tolerated or a Property that can be Managed?cited by 0