Why don't software developers use static analysis tools to find bugs?
The DOI matches its Crossref record; 23 of the 23 references it cites were found in a registry or an index.
Abstract
Using static analysis tools for automating code inspections can be beneficial for software engineers. Such tools can make finding bugs, or software defects, faster and cheaper than manual inspections. Despite the benefits of using static analysis tools to find bugs, research suggests that these tools are underused. In this paper, we investigate why developers are not widely using static analysis tools and how current tools could potentially be improved. We conducted interviews with 20 developers and found that although all of our participants felt that use is beneficial, false positives and the way in which the warnings are presented, among other things, are barriers to use. We discuss several implications of these results, such as the need for an interactive mechanism to help developers fix defects.
Overview
Integrity signals
Registry
Cites
Statistics
Verification
Claims the paper makes
Claims other papers make about this one
Each is checked against this paper’s own text: does it say what the citing paper says it does?
In the citing paper
“industry reports show that it is difficult to get developers to adopt static analysis in their workflows [5, 11, 30, 34].”
From Position: Vibe Coding Needs Vibe Reasoning: Improving Vibe Coding with Formal Verification (2025) · cites this paper as [11]
Citations
Cites
(2005) · Texas ScholarWorks (Texas Digital Library) · Cited by 1,064
A few billion lines of code later: using static analysis to find bugs in the real world
Bessey, A., Block, K., Chelf, B., Chou, A., Fulton, B., Hallem, S., Henri-Gros, C., Kamsky, A., McPeak, S., & Engler, D. (2010) · Communications of the ACM · doi:10.1145/1646353.1646374 · Cited by 635
Using Static Analysis to Find Bugs
Ayewah, N., Pugh, W., Hovemeyer, D., Morgenthaler, J. D., & Penix, J. (2008) · IEEE Software · doi:10.1109/ms.2008.130 · Cited by 534
Experiences from Conducting Semi-structured Interviews in Empirical Software Engineering Research
Hove, S. E., & Anda, B. (2005) · 11th IEEE International Software Metrics Symposium (METRICS'05) · doi:10.1109/metrics.2005.24 · Cited by 345
Mylar: a degree-of-interest model for IDEs
Kersten, M., & Murphy, G. C. (2005) · Proceedings of the 4th international conference on Aspect-oriented software development · doi:10.1145/1052898.1052912 · Cited by 298
Johnson, S. C., & Hill, M. G. (1978) · Cited by 280
Static analysis tools as early indicators of pre-release defect density
Nagappan, N., & Ball, T. (2005) · Proceedings of the 27th international conference on Software engineering - ICSE '05 · doi:10.1145/1062455.1062558 · Cited by 272
Secure Programming with Static Analysis
Chess, B., & West, J. (2007) · Cited by 224
Refactoring Tools: Fitness for Purpose
Murphy-Hill, E., & Black, A. P. (2008) · IEEE Software · doi:10.1109/ms.2008.123 · Cited by 155
Self-citationAn interactive ambient visualization for code smells
Murphy-Hill, E., & Black, A. P. (2010) · Proceedings of the 5th international symposium on Software visualization · doi:10.1145/1879211.1879216 · Cited by 147
Self-citation
Research works printed but not linked: 10
- 0, KLOCwork inSight
- 0, Microsoft Visual Studio
- 0, Google CodePro Analytix
- robertson, 2004, Impact of interruption style on enduser debugging, Proc CHI, 287
- lewis, 1982, Using the "Thinking Aloud" Method in Cognitive Interface Design
- 0, Eclipse
- gordon, 1998, Coding interview responses, Basic Interviewing Skills Waveland Pr Inc, 183
- 0, FindBugs
- 0, IntelliJ IDEA
- 0, Netbeans
Cited by
Items 301–400 of 567
Fuzzing, Symbolic Execution, and Expert Guidance for Better Testing
Kadron, İ. B., Noller, Y., Padhye, R., Bultan, T., Păsăreanu, C. S., & Sen, K. (2023) · IEEE Software · doi:10.1109/ms.2023.3237981 · Cited by 7
“Similarly, there are existing works for debugging 16 and static analysis 17 showing that assumptions made by automated techniques often do not hold in practice.”
BackgroundVulNet: Towards improving vulnerability management in the Maven ecosystem
Ma, Z., Mondal, S., Chen, T.-H. P., Zhang, H., & Hassan, A. E. (2024) · Empirical Software Engineering · doi:10.1007/s10664-024-10448-6 · Cited by 9
Automatic Data Labeling for Software Vulnerability Prediction Models: How Far Are We?
Le, T. H. M., & Babar, M. A. (2024) · Proceedings of the ... ACM-IEEE International Symposium on Empirical Software Engineering and Measurement/International Symposium on Empirical Software Engineering and Measurement · doi:10.1145/3674805.3686675 · Cited by 14
“Section 7 concludes the study.”
Nunes, P., Fonseca, J., & Vieira, M. P. A. (2024) · IEEE Access · doi:10.1109/access.2024.3522094 · Cited by 7
“However, this process is also likely to generate more FPs, since it is well-known that using more tools increase both TP and FP [37], [39].”
DyLin: A Dynamic Linter for Python
Eghbali, A., Burk, F., & Pradel, M. (2025) · Proceedings of the ACM on software engineering. · doi:10.1145/3729395 · Cited by 5
“Notably, this distinguished DyLin from static linting, which often suffers from low precision [21, 22, 41].”
Efficient Pattern-based Static Analysis Approach via Regular-Expression Rules
Zhang, X., Zhou, Y., & Tan, S. H. (2023) · IEEE International Conference on Software Analysis, Evolution and Reengineering (SANER) · doi:10.1109/saner56733.2023.00022 · Cited by 8
CryptoShield - Automatic On-Device Mitigation for Crypto API Misuse in Android Applications
Draschbacher, F., & Feichtner, J. (2023) · ACM Asia Conference on Computer and Communications Security (ASIA CCS) · doi:10.1145/3579856.3582832 · Cited by 5
“However, this method has proven to be imprecise in real-world scenarios [7, 13, 14], suffering from a high degree of false positives due to unreachable code and false negatives due to dynamically loaded code, complex data dependencies or obfuscation.”
MethodProgrammer Stories, Stories for Programmers: Exploring Storytelling in Software Development
Wuilmart, P., Söderberg, E., & Höst, M. (2023) · International Conference on Art, Science, and Engineering of Programming (<Programming>) · doi:10.1145/3594671.3594677 · Cited by 5
“We note that this is similar to what has been reported on the use of static analysis tools [8].”
ResultStatic Code Analysis: A Tree of Science Review
Ruiz, G. A., Robledo, S., & Morales, H. H. (2023) · Entre ciencia e ingeniería · doi:10.31908/19098367.2846 · Cited by 5
“Johnson et al. [24] conducted several interviews with developers and identified the same problems with false positives.”
BatFix: Repairing language model-based transpilation
Ramos, D., Lynce, I., Manquinho, V. M., Martins, R., & Goues, C. L. (2024) · ACM Transactions on Software Engineering and Methodology · doi:10.1145/3658668 · Cited by 16
“Developers dislike (and distrust) tools that make unpredictable or “silly” mistakes [29].”
Adoption of automated software engineering tools and techniques in Thailand
Ragkhitwetsagul, C., Krinke, J., Choetkiertikul, M., Sunetnanta, T. T., & Sarro, F. (2024) · Empirical Software Engineering · doi:10.1007/s10664-024-10472-6 · Cited by 10
BAFLineDP: Code Bilinear Attention Fusion Framework for Line- Level Defect Prediction
Qiu, S., Huang, H., Luo, J., Kuang, Y., & Luo, H. (2024) · IEEE International Conference on Software Analysis, Evolution and Reengineering (SANER) · doi:10.1109/saner60148.2024.00036 · Cited by 13
“One of the simplest methods is to use static analysis tools to identify defective lines of code based on predefined rules [25].”
BackgroundMethodCross Domain Few-Shot Line-Level Defect Prediction in Open Software Development via Meta Learning
Li, Z., Guo, S., Zhang, L., Li, H., Yang, Z., Qiao, N., & Ma, Q. (2025) · IEEE Transactions on Consumer Electronics · doi:10.1109/tce.2025.3572334 · Cited by 6
Improving prioritization of software weaknesses using security models with AVUS
Renatus, S., Bartelheimer, C., & Eichler, J. (2015) · IEEE International Working Conference on Source Code Analysis and Manipulation (SCAM) · doi:10.1109/scam.2015.7335423 · Cited by 5
A Parallel Worklist Algorithm for Modular Analyses
Es, N. V., Stiévenart, Q., der Plas, J. V., & Roover, C. D. (2020) · IEEE International Working Conference on Source Code Analysis and Manipulation (SCAM) · doi:10.1109/scam51674.2020.00006 · Cited by 5
“Consequently, a combination of high precision and high performance is harder to achieve, and the lack of performance is often mentioned as one of the prime reasons why developers eschew the usage of static analysers altogether [4], [14], [27].”
BackgroundLaverdière, M.-A., Julien, K., & Merlo, E. (2021) · Information and Software Technology · doi:10.1016/j.infsof.2021.106630 · Cited by 5
A Self-adaptive Approach for Assessing the Criticality of Security-Related Static Analysis Alerts
Siavvas, M., Kalouptsoglou, I., Tsoukalas, D., & Kehagias, D. D. (2021) · Lecture notes in computer science · doi:10.1007/978-3-030-87007-2_21 · Cited by 8
Tool Support for Teaching Hoare Logic
Sznuk, T., & Schubert, A. (2014) · Lecture notes in computer science · doi:10.1007/978-3-319-10431-7_27 · Cited by 5
Zhi, C., Deng, S., Han, J., & Yin, J. (2021) · Automated Software Engineering · doi:10.1007/s10515-021-00317-7 · Cited by 7
“In fact, the prioritization of results is an important feature of such static-analysis-based bug-finding tools (Johnson et al. 2013).”
BackgroundEvaluating and improving transformers pre-trained on ASTs for Code Completion
Ochs, M., Narasimhan, K., & Mezini, M. (2023) · IEEE International Conference on Software Analysis, Evolution, and Reengineering · doi:10.1109/saner56733.2023.00096 · Cited by 8
“However, static analysis is known to suffer from false positives [7].”
BackgroundCause Points Analysis for Effective Handling of Alarms
Muske, T., & Khedker, U. P. (2016) · Proceedings/Proceedings - International Symposium on Software Reliability Engineering · doi:10.1109/issre.2016.45 · Cited by 5
“The environment extension is to integrate the inspection of alarms seamlessly into their development process, which currently many of the static analysis tools lack today [12].”
BackgroundMethodInfluentialYan, M. L., Zhang, X., Xu, L., Hu, H., Sun, S., & Xia, X. (2017) · IEEE Annual International Computer Software and Applications Conference (COMPSAC) · doi:10.1109/compsac.2017.201 · Cited by 5
Toward Proactive Refactoring: An Exploratory Study on Decaying Modules
Sae‐Lim, N., Hayashi, S., & Saeki, M. (2019) · IEEE/ACM International Workshop on Refactoring (IWoR) · doi:10.1109/iwor.2019.00015 · Cited by 5
Cyber Resilient Flight Software for Spacecraft
Wheeler, W. A., Cohen, N., Betser, J., & Ewart, R. M. (2018) · AIAA SPACE and Astronautics Forum and Exposition · doi:10.2514/6.2018-5220 · Cited by 5
EDATA: Energy Debugging And Testing for Android
Blokland, E., Cruz, L., & Arie Van Deursen, A. (2025) · IEEE/ACM International Conference on Mobile Software Engineering and Systems (MOBILESoft) · doi:10.1109/mobilesoft66462.2025.00017 · Cited by 4
“Johnson et al. found that missing one or more of the “what, why, and how to fix” is a significant barrier in the adoption of analysis tools [4].”
Predicting Software Flaws with Low Complexity Models based on Static Analysis Data
Meirelles, P., Kanashiro, L., Ribeiro, A., Silva, D., & Terceiro, A. S. D. A. (2018) · Journal of Information Systems Engineering & Management · doi:10.20897/jisem.201817 · Cited by 4
“It is also known that static analysis helps programmers detect software vulnerabilities before they reach production (Evans and Larochelle, 2002) in a cheaper way than solely conducting manual inspections (Johnson et al., 2013), thus the interest in static analyzers.”
BackgroundA Survival Analysis-Based Prioritization of Code Checker Warning: A Case Study Using PMD
Aman, H., Amasaki, S., Yokogawa, T., & Kawahara, M. (2019) · Studies in computational intelligence · doi:10.1007/978-3-030-24405-7_5 · Cited by 8
Static Vulnerability Analysis Using Intermediate Representations: A Literature Review
Spanier, A., & Mahoney, W. (2023) · European Conference on Cyber Warfare and Security · doi:10.34190/eccws.22.1.1154 · Cited by 4
An AST-Based Code Change Representation and Its Performance in Just-in-Time Vulnerability Prediction
Aladics, T., Hegedűs, P., & Ferenć, R. (2023) · Communications in computer and information science · doi:10.1007/978-3-031-37231-5_8 · Cited by 6
Reduction of False Positives for Runtime Errors in C/C++ Software: A Comparative Study
Park, J., Shin, J., & Choi, B. (2023) · Electronics · doi:10.3390/electronics12163518 · Cited by 4
RULER: Prebugging with Proxy-Based Programming
Repenning, A., & Basawapatna, A. R. (2024) · IEEE Symposium on Visual Languages and Human-Centric Computing (VL/HCC) · doi:10.1109/vl/hcc60511.2024.00037 · Cited by 4
“Static code analysis [27] visualizes semantic problems such as unreachable code.”
BackgroundUnderstanding Test Convention Consistency as a Dimension of Test Quality
Robillard, M. P., Nassif, M., & Sohail, M. (2024) · ACM Transactions on Software Engineering and Methodology · doi:10.1145/3672448 · Cited by 5
On the detection and analysis of software security vulnerabilities
Wijesiriwardana, C., & Wimalaratne, P. (2017) · International Conference on IoT and Application (ICIOT) · doi:10.1109/iciota.2017.8073635 · Cited by 4
Fixing Vulnerabilities Automatically with Linters
Rafnsson, W., Giustolisi, R., Kragerup, M., & Høyrup, M. (2020) · Lecture notes in computer science · doi:10.1007/978-3-030-65745-1_13 · Cited by 6
A parallel worklist algorithm and its exploration heuristics for static modular analyses
Stiévenart, Q., Es, N. V., der Plas, J. V., & Roover, C. D. (2021) · Journal of Systems and Software · doi:10.1016/j.jss.2021.111042 · Cited by 4
Provable GPU Data-Races in Static Race Detection
Liew, D., Cogumbreiro, T., & Lange, J. (2022) · Electronic Proceedings in Theoretical Computer Science · doi:10.4204/eptcs.356.4 · Cited by 4
“Further, research shows that false alarms hamper the adoption of static analysis in industrial settings [7,16].”
BackgroundVert, T., Krikun, T., & Игоревич, Г. М. (2013) · Tools and Methods of Program Analysis (TMPA) · doi:10.1109/tmpa.2013.7163724 · Cited by 4
Understanding automated code review process and developer experience in industry
Kim, H., Kwon, Y., Joh, S., Kwon, H., Ryou, Y., & Kim, T. (2022) · ACM Joint European Software Engineering Conference and Symposium on the Foundations of Software Engineering (ESEC/FSE) · doi:10.1145/3540250.3558950 · Cited by 6
“The tools are not only used by open-source projects, but also by many industries in practice to validate and verify the code base in spite of false positives [3, 13].”
BackgroundTeaching Computer Science Students to Communicate Scientific Findings More Effectively
Wyrich, M., & Wagner, S. (2023) · IEEE/ACM International Conference on Software Engineering: Software Engineering Education and Training (ICSE-SEET) · doi:10.1109/icse-seet58685.2023.00017 · Cited by 5
A Survey of Tool Support for Working with Design Decisions in Code
Mehrpour, S., & LaToza, T. D. (2023) · ACM Computing Surveys · doi:10.1145/3607868 · Cited by 7
“Several studies have examined the usability issues involved with using static analysis tools (e.g., References [38, 73]) and proposed suggestions to mitigate common issues, such as configuring the priority of errors based on development contexts (e.g., local programming, continuous integration, or code review) [152],…”
BackgroundMethodInfluentialAutomatic Testing and Benchmarking for Configurable Static Analysis Tools
Mordahl, A. (2023) · ACM SIGSOFT International Symposium on Software Testing and Analysis (ISSTA) · doi:10.1145/3597926.3605232 · Cited by 6
“However, configurable static analysis faces obstacles to wide-spread adoption [12, 30].”
BackgroundInteractive abstract interpretation: reanalyzing multithreaded C programs for cheap
Erhard, J., Saan, S., Tilscher, S., Schwarz, M. H., Holter, K., Vojdani, V., & Seidl, H. (2024) · International Journal on Software Tools for Technology Transfer · doi:10.1007/s10009-024-00768-9 · Cited by 4
SQL-Identifier Injection Attacks
Cetin, C., Goldgof, D. B., & Ligatti, J. (2019) · IEEE Conference on Communications and Network Security · doi:10.1109/cns.2019.8802743 · Cited by 4
Automatically Customizing Static Analysis Tools to Coding Rules Really Followed by Developers
Ueda, Y., Ishio, T., & Matsumoto, K. (2021) · IEEE International Conference on Software Analysis, Evolution and Reengineering (SANER) · doi:10.1109/saner50967.2021.00062 · Cited by 4
Teaching Correctness-by-Construction and Post-hoc Verification – The Online Experience
Runge, T., Bordis, T., Thüm, T., & Schaefer, I. (2021) · Lecture notes in computer science · doi:10.1007/978-3-030-91550-6_8 · Cited by 4
What Do We Know About Buffer Overflow Detection?
Chaim, M. L., Santos, D. S., & Cruzes, D. S. (2018) · International Journal of Systems and Software Security and Protection · doi:10.4018/ijsssp.2018070101 · Cited by 4
Developers' Perspective on Today's and Tomorrow's Programming Tool Assistance: A Survey
Kuang, P., Söderberg, E., & Höst, M. (2024) · International Conference on Art, Science, and Engineering of Programming (<Programming>) · doi:10.1145/3660829.3660848 · Cited by 6
“The usability problems of program analysis are similar to those reported in the literature, e.g., issues connected to the quality of the results and their presentation [10, 11].”
Zhou, Y., Tang, H., Zhu, L., Ding, H., & Qian, J. (2025) · ACM Transactions on Software Engineering and Methodology · doi:10.1145/3707456 · Cited by 3
“SATs play a principal role in the domain of CLBI, comprising a set of tools that scrutinize source or binary code without executing the program [13, 14, 23, 25–28].”
Unveiling security weaknesses in autonomous driving systems: An in-depth empirical study
Cheng, W., Li, Z., Liang, P., Mo, R., & Liu, H. (2025) · Information and Software Technology · doi:10.1016/j.infsof.2025.107709 · Cited by 5
“The method faces challenges as being resource-intensive, and its complexity may lead to a high rate of false positives, which can undermine the confidence of developers in the efficacy of the tools (Johnson et al., 2013; Ruthruff et al., 2008).”
SafeRace: Assessing and Addressing WebGPU Memory Safety in the Presence of Data Races
Levine, R., Lee, A., Abbas, N., Little, K., & Sorensen, T. (2025) · Proceedings of the ACM on Programming Languages · doi:10.1145/3763075 · Cited by 4
Facilitating Trust in AI-assisted Software Tools
Johnson, B., Bird, C., Ford, D., Haque, E. A., Forsgren, N., & Zimmermann, T. (2026) · ACM Transactions on Software Engineering and Methodology · doi:10.1145/3772370 · Cited by 12
“As we continue to struggle with tool adoption and use in practice, the tool landscape continues to evolve with technology.”
Self-citationContext-Aware Code Review Automation: A Retrieval-Augmented Approach
İçöz, B., & Biricik, G. (2026) · Applied Sciences · doi:10.3390/app16041875 · Cited by 7
Security Monitoring during Software Development: An Industrial Case Study
Siavvas, M., Tsoukalas, D., Kalouptsoglou, I., Manganopoulou, E., Manolis, G., Kehagias, D. D., & Tzovaras, D. K. (2023) · Applied Sciences · doi:10.3390/app13126872 · Cited by 8
Building a Framework to Improve the User Experience of Static Analysis Tools
Schlichtig, M. (2024) · ACM/IEEE International Conference on Software Engineering: Companion Proceedings (ICSE-Companion) · doi:10.1145/3639478.3639813 · Cited by 6
“This follows in line with previous research on the topic of usability of static analysis tools [12, 16, 23, 29, 36, 40].”
BackgroundResultBennett, G., Hall, T., Counsell, S., Winter, E., & Shippey, T. (2024) · Proceedings of the ... ACM-IEEE International Symposium on Empirical Software Engineering and Measurement/International Symposium on Empirical Software Engineering and Measurement · doi:10.1145/3674805.3690750 · Cited by 3
“It is well known that static analysis tools produce a large number of false positives; studies have concluded the high false positives rate is a burden to developers [20, 21] and recommend reducing the false positive rate of ASATs.”
The Potential of LLM-Generated Reports in DevSecOps
Lykousas, N., Argyropoulos, V., & Casino, F. (2025) · Learning and analytics in intelligent systems · doi:10.1007/978-3-031-98410-5_27 · Cited by 4
“Nevertheless, many of the available security tools frequently produce inaccurate results or irrelevant results (e.g., false positives and negatives) [4], requiring the software teams to manually assess such outputs.”
BackgroundImproving Long-Tail Vulnerability Detection Through Data Augmentation Based on Large Language Models
Deng, X., Duan, F., Xie, R., Ye, W., & Zhang, S. (2024) · IEEE International Conference on Software Maintenance (ICSM) · doi:10.1109/icsme58944.2024.00033 · Cited by 6
Liu, X., Zhou, Y., Tang, Y., Qian, J., & Zhou, Y. (2025) · Science of Computer Programming · doi:10.1016/j.scico.2025.103296 · Cited by 11
Enhancing line-level defect prediction using bilinear attention fusion and ranking optimization
Qiu, S., Huang, H., Kuang, Y., Luo, H., & Liu, X. (2025) · Empirical Software Engineering · doi:10.1007/s10664-025-10674-6 · Cited by 5
Understanding Industry Perspectives of Static Application Security Testing (SAST) Evaluation
Li, Y., Yao, P., Yu, K., Wang, C., Ye, Y., Li, S., Luo, M., Liu, Y., & Ren, K. (2025) · Proceedings of the ACM on software engineering. · doi:10.1145/3729404 · Cited by 3
“” (P7) Indeed, previous research [44, 82] has emphasized the importance of integrating SASTs into developers’ workflows.”
InfluentialExtending Static Code Analysis with Application-Specific Rules by Analyzing Runtime Execution Traces
Ersoy, E., & Sözer, H. (2016) · Communications in computer and information science · doi:10.1007/978-3-319-47217-1_4 · Cited by 3
“Static code analysis tools (SCAT) can detect the violation of programming rules by checking (violation of) patterns throughout the source code [1].”
BackgroundSurvey on static program analysis results refinement approaches
Gerasimov, A. Y. (2017) · Proceedings of the Institute for System Programming of RAS · doi:10.15514/ispras-2017-29(3)-6 · Cited by 3
Designing UIs for Static Analysis Tools
Tiganov, D., Quang, L. N., & Ali, K. (2021) · Queue · doi:10.1145/3487019.3487026 · Cited by 4
“11,13,15 SWAN is being created with responsiveness in mind.”
BackgroundDevelopers’ viewpoints to avoid bug-introducing changes
Souza, J., Lima, R., Fonseca, B., Cartaxo, B., Ribeiro, M., Pinto, G., Gheyi, R., & Garcia, A. (2021) · Information and Software Technology · doi:10.1016/j.infsof.2021.106766 · Cited by 5
Using Multiple Code Representations to Prioritize Static Analysis Warnings
Vu, T. T., & Vo, H. D. (2022) · International Conference on Knowledge and Systems Engineering/Proceedings · doi:10.1109/kse56063.2022.9953786 · Cited by 3
ViolationTracker: Building Precise Histories for Static Analysis Violations
Yu, P., Wu, Y., Peng, X., Peng, J., Zhang, J., Xie, P., & Zhao, W. (2023) · ACM/IEEE International Conference on Software Engineering: Companion Proceedings (ICSE-Companion) · doi:10.1109/icse48619.2023.00171 · Cited by 3
“Violations are detected on specific revisions, or snapshots , of a project by certain ASATs.”
BackgroundInfluentialGroppe, J., Groppe, S., Senf, D., & Möller, R. (2024) · Information · doi:10.3390/info15040216 · Cited by 3
On Secret Management and Handling in Mobile Application Development Life Cycle: A Position Paper
Bunyakiati, P., & Sammapun, U. (2019) · IEEE/ACM International Conference on Automated Software Engineering Workshops (ASEW) · doi:10.1109/asew.2019.00033 · Cited by 3
“[19] show that effectiveness of stateof-the-art static analysis tools can be increased by improving their usability.”
BackgroundProvenance-Based Security Audits and Its Application to COVID-19 Contact Tracing Apps
Schreiber, A., Sonnekalb, T., Heinze, T. S., von Kurnatowski, L., Gonzalez-Barahona, J. M., & Packer, H. S. (2021) · Lecture notes in computer science · doi:10.1007/978-3-030-80960-7_6 · Cited by 3
An Empirical Assessment on Merging and Repositioning of Static Analysis Alarms
Mansoor, N., Muske, T., Serebrenik, A., & Sharif, B. (2022) · IEEE International Working Conference on Source Code Analysis and Manipulation (SCAM) · doi:10.1109/scam55253.2022.00031 · Cited by 3
On implementational variations in static analysis tools
Muske, T., & Bokil, P. (2015) · IEEE International Conference on Software Analysis, Evolution and Reengineering (SANER) · doi:10.1109/saner.2015.7081867 · Cited by 3
“This is needed since many users report that the results of the static analysis tools are not easily comprehended [6].”
BackgroundStatic Analysis Alert Audits: Lexicon & Rules
Svoboda, D., Flynn, L., & Snavely, W. (2016) · IEEE Cybersecurity Development (SecDev) · doi:10.1109/secdev.2016.018 · Cited by 3
5W+1H Static Analysis Report Quality Measure
Menshikov, M., & Андреевич, Л. Т. (2017) · Communications in computer and information science · doi:10.1007/978-3-319-71734-0_10 · Cited by 3
The Impact of Interface Design on the Usability of Code Analyzers
Nembhard, F., & Carvalho, M. (2019) · IEEE SoutheastCon · doi:10.1109/southeastcon42311.2019.9020339 · Cited by 5
“Research shows that developers and programmers are skeptical of using a lot of existing code analyzers [2].”
BackgroundSo {U} R CERER: Developer-Driven Security Testing Framework for Android Apps
Rahman, M. S., Kojusner, B., Kennedy, R., Pathak, P., Qi, L., & Williams, B. J. (2021) · IEEE/ACM International Conference on Automated Software Engineering Workshops (ASEW) · doi:10.1109/asew52652.2021.00020 · Cited by 3
Patching Locking Bugs Statically with Crayons
Cruz-Carlón, J. A., Varshosaz, M., Goues, C. L., & Wąsowski, A. (2022) · ACM Transactions on Software Engineering and Methodology · doi:10.1145/3548684 · Cited by 5
“The fact that fixing statically identified bugs remains a largely manual process is a barrier to widespread adoption of such tools [25, 26].”
BackgroundClassification and Ranking of Delta Static Analysis Alarms
Muske, T., & Serebrenik, A. (2022) · IEEE International Working Conference on Source Code Analysis and Manipulation (SCAM) · doi:10.1109/scam55253.2022.00029 · Cited by 3
Identifying Personal Data Processing for Code Review
Tang, F., Østvold, B. M., & Bruntink, M. (2023) · International Conference on Information Systems Security and Privacy (ICISSP) · doi:10.5220/0011725700003405 · Cited by 3
“Johnson et al. (Johnson et al., 2013) pointed out that “because the results are dumped onto a code re-viewer’s screen with no distinct structure causing him to spend a lot of time trying to figure out what needs to be done”.”
BackgroundThe Human Dimension of Software Security and Factors Affecting Security Processes
Assal, H. (2018) · Carleton University's Institutional Repository (MacOdrum Library, Carleton University) · doi:10.22215/etd/2018-13347 · Cited by 4
“In comparison to manual line-by-line code inspection, SATs offer an automated process, making fault detection faster and less effortful.”
BackgroundMethodResultInfluentialGradual Program Analysis for Null PointersPreprint
Estep, S., Wise, J., Aldrich, J., Tanter, É., Bader, J., & Sunshine, J. (2021) · arXiv (Cornell University) · doi:10.4230/lipics.ecoop.2021.3 · Cited by 3
Abstract Debuggers: Exploring Program Behaviors using Static Analysis Results
Holter, K., Hennoste, J. O., Lam, P., Saan, S., & Vojdani, V. (2024) · ACM SIGPLAN International Symposium on New Ideas, New Paradigms, and Reflections on Programming and Software (Onward!) · doi:10.1145/3689492.3690053 · Cited by 13
Understanding mobile-specific code smells
Habchi, S. (2019) · theses.fr (ABES) · doi:10.70675/1b95cb5czc2cdz4e09zb3e4zeae4ed6f6462 · Cited by 4
“• We confirm the importance of priority and severity indicators in static analysis tools [35, 47, 114].”
BackgroundResultInfluentialA Model-Driven Approach for the Management and Enforcement of Coding Conventions
Rodrigues, E., Pereira, J. D., & Montecchi, L. (2023) · IEEE Access · doi:10.1109/access.2023.3256886 · Cited by 2
“Johnson et al. interviewed 20 developers, and 17 of them complained that many tools are not trivial to configure, even to the point of being ‘‘so hard to configure, they prevent you from doing anything’’ [14].”
BackgroundA Just-in-time Software Defect Detection Method Using Generative Adversarial Networks
Luo, N., Ma, Y., Li, J., & Xie, Y. (2023) · International Conference on Electronic Communication and Artificial Intelligence (ICECAI) · doi:10.1109/icecai58670.2023.10176967 · Cited by 2
“Some studies have shown that many developers tend to ignore the classification results of the detection model[6-7], assuming that their committed changes will not cause defects and that developers only make semantic preserving changes to the submitted changes, rather than modifying the logic, to get the detection mode…”
BackgroundOn the Relationship between Code Verifiability and Understandability
Feldman, K., Kellogg, M., & Chaparro, O. (2023) · ACM Joint European Software Engineering Conference and Symposium on the Foundations of Software Engineering (ESEC/FSE) · doi:10.1145/3611643.3616242 · Cited by 6
“Though veri fi cation and static analysis tools are becoming more common in industry [8, 75], studies of their use and the challenges developers face in deploying them [8, 57, 63, 84, 98] suggest that false positives remain a problem in practice [42, 63].”
BackgroundA Method for Processing Static Analysis Alarms Based on Deep Learning
Tan, Y., & Tian, J. (2024) · Applied Sciences · doi:10.3390/app14135542 · Cited by 4
AI-Enhanced Static Analysis: Reducing False Alarms Using Large Language Models
Apostolidis, G. D., Kalouptsoglou, I., Siavvas, M., Kehagias, D. D., & Tzovaras, D. K. (2025) · IEEE International Conference on Smart Computing · doi:10.1109/smartcomp65954.2025.00088 · Cited by 3
From Overload to Insight: Bridging Code Search and Code Review with LLMs
Rao, N., Vasilescu, B., & Holmes, R. (2025) · ACM Joint European Software Engineering Conference and Symposium on the Foundations of Software Engineering (ESEC/FSE) · doi:10.1145/3696630.3728518 · Cited by 4
“Unfortunately, many of these tools go underutilized [7], especially during code review [5], one commonly-used checkpoint for ensuring that changes made to software systems do not degrade its quality [3, 9].”
Are We SOLID Yet? An Empirical Study on Prompting LLMs to Detect Design Principle Violations
Pehlivan, F., Ergüzen, A. Ü., Moslemi, S., Lami, M., & Koyuncu, A. (2025) · IEEE/ACM International Conference on Automated Software Engineering (ASE) · doi:10.1109/ase63991.2025.00350 · Cited by 2
“1: Overview of the approach an LLM via a tailored prompt to predict a potential SOLID violation.”
Devsecops-Driven Security Controls for ERP Release Pipelines
Gangaiah, Y. K., Pappu, K., & Thanvi, Y. S. (2026) · International Symposium on Digital Forensics and Security (ISDFS) · doi:10.1109/isdfs69419.2026.11459076 · Cited by 7
“The zero false-positive rate (precision = 1.00) avoids the developer distrust that false alarms cause in automated gates [23].”
InfluentialCritical Understanding of Security Vulnerability Detection Plugin Evaluation Reports
Beba, S., Karlsen, M. M., Li, J., & Zhang, B. (2021) · Asia-Pacific Software Engineering Conference (APSEC) · doi:10.1109/apsec53868.2021.00035 · Cited by 2
“The results of [1] show that the plugins have much higher false-negative and false-positive rates than the level (as explained in [17] [13] [18]) that developers are willing to accept.”
BackgroundDevReplay: Linter that generates regular expressions for repeating code changes
Ueda, Y., Ishio, T., & Matsumoto, K. (2022) · Science of Computer Programming · doi:10.1016/j.scico.2022.102857 · Cited by 2
WINE: Warning miner for improving bug finders
Choi, Y.-H., & Nam, J. (2022) · Information and Software Technology · doi:10.1016/j.infsof.2022.107109 · Cited by 2
Complementing Secure Code Review with Automated Program Analysis
Charoenwet, W. (2023) · ACM/IEEE International Conference on Software Engineering: Companion Proceedings (ICSE-Companion) · doi:10.1109/icse-companion58688.2023.00052 · Cited by 2
“However, automated program analysis still has some disadvantages such as a high number of false warnings for static analysis and the long execution time for dynamic analysis [9], [10], making the tools unfit for some situations.”
BackgroundBugsplainer: Leveraging Code Structures to Explain Software Bugs with Neural Machine Translation
Mahbub, P., Rahman, M. M., Shuvo, O., & Avinash, G. (2023) · IEEE International Conference on Software Maintenance (ICSM) · doi:10.1109/icsme58846.2023.00067 · Cited by 2
A Comparative Study of Commit Representations for JIT Vulnerability Prediction
Aladics, T., Hegedűs, P., & Ferenć, R. (2024) · Computers · doi:10.3390/computers13010022 · Cited by 3
Do Static Analysis Tools Improve Awareness and Attitude Toward Secure Software Development?
Nocera, S., Romano, S., Nucci, D. D., Francese, R., Palomba, F., & Scanniello, G. (2024) · Communications in computer and information science · doi:10.1007/978-3-031-70245-7_28 · Cited by 2
Leveraging Context Information for Self-Admitted Technical Debt Detection
Yonekura, M., Kashiwa, Y., Lin, B., Fujiwara, K., & Iida, H. (2025) · IEEE International Conference on Program Comprehension (ICPC) · doi:10.1109/icpc66645.2025.00018 · Cited by 5
“Previous studies [33], [34] show that software development support tools tend not to be adopted when they exhibit a high false positive rate.”
Treating software quality as a first-class entity
Tymchuk, Y. (2015) · IEEE International Conference on Software Maintenance (ICSM) · doi:10.1109/icsm.2015.7332521 · Cited by 2
“During a code review session, tools like Review Bot [21] use static analysis reports to improve reviewers experience by pointing out parts that violate some rules.”
MethodSymbolic Execution with Finite State Automata
Fülöp, E., & Pataki, N. (2019) · IEEE International Scientific Conference on Informatics (Informatics) · doi:10.1109/informatics47936.2019.9119287 · Cited by 2
“While most static analysis methods are designed to detect anomalies (called bugs) in software code, the methods they employ are varied [3].”
Background
Metadata
- Authors
- Johnson, B., Song, Y., Murphy-Hill, E., & Bowdidge, R.
- Affiliations
- North Carolina State University (US)
- Google (United States) (US)
- Venue
- 2013 35th International Conference on Software Engineering (ICSE)
- Publisher
- IEEE
- Published
- 2013-05
- Pages
- 672-681
- ISSN
- 0270-5257 (ISSN-L)
- OpenAlex
- W4233410239
- Cited by
- 568
- References
- 23
- Citations by year
- 2026: 58 · 2025: 58 · 2024: 66 · 2023: 73 · 2022: 65 · 2021: 53 · 2020: 46 · 2019: 41 · 2018: 27 · 2017: 38 · 2016: 21 · 2015: 14 · 2014: 5 · 2013: 3
- FWCI
- 11.51
- Type
- conference paper
- Language
- en
- Open access
- closed
- Locations
- ACM/IEEE International Conference on Software Engineering: Companion Proceedings (ICSE-Companion) (publishedVersion)
- Topics
- Physical Sciences › Computer Science › Information Systems › Software Engineering Research
- Physical Sciences › Computer Science › Software › Software Testing and Debugging Techniques
- Physical Sciences › Computer Science › Information Systems › Software Engineering Techniques and Practices
- Keywords
- static analysis tools, software defect detection, bug detection, false positives, developer behavior
About these checks
Registry, retraction, Cites and statistics results are computed, not judged, with one exception: a printed reference that no index lists is read once by a model before it counts as a citation error. Claims are extracted by a model and kept only when their quote appears verbatim in the text; each cited source is then checked, with a model’s help, for whether it says what the claim relies on. Those verdicts can be wrong — read the claim’s quote and the cited source before relying on one.
Statistics and arithmetic are recomputed, not judged.
Confidence bands are shown only for fields calibrated on our annotated test set. None is calibrated yet, so no band is shown.
What counts as a claim ›How we measure confidence ›How we check this ›
Are you an author, or do you see a problem with this page? Request a review
Data sources
Bibliographic data: Semantic Scholar, OpenAlex, Crossref.
Contains information from the Semantic Scholar Academic Graph Datasets, made available under the ODC Attribution License (ODC-BY 1.0).
Semantic Scholar’s data is described in: Kinney, R., et al. (2023). The Semantic Scholar Open Data Platform. arXiv:2301.10140.