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 201–300 of 567
What to Fix? Distinguishing between Design and Non-design Rules in Automated Tools
Ernst, N., Bellomo, S., Özkaya, İ., & Nord, R. L. (2017) · IEEE International Conference on Software Architecture (ICSA) · doi:10.1109/icsa.2017.25 · Cited by 14
“[1] write about interviews they did at Google with twenty developers asking how they used Lint, Findbugs etc.”
BackgroundMethodInfluentialA solver-aided language for test input generation
Ringer, T., Grossman, D., Schwartz‐Narbonne, D., & Taşiran, S. (2017) · Proceedings of the ACM on Programming Languages · doi:10.1145/3133915 · Cited by 15
“The goal of Iorek is to give developers the benefit of a test generation framework without any additional cost, given that developers are resistant to tools that disrupt development flow (Johnson et al. 2013).”
BackgroundFlower: Navigating program flow in the IDE
Smith, J., Brown, C., & Murphy-Hill, E. R. (2017) · IEEE Symposium on Visual Languages and Human-Centric Computing (VL/HCC) · doi:10.1109/vlhcc.2017.8103445 · Cited by 16
“Barriers to invocation inhibit adoption [9].”
Self-citationComparing Correctness-by-Construction with Post-Hoc Verification—A Qualitative User Study
Runge, T., Thüm, T., Cleophas, L., Schaefer, I., & Watson, B. W. (2020) · Lecture notes in computer science · doi:10.1007/978-3-030-54997-8_25 · Cited by 18
“[23] interviewed developers about the use of static analysis tools.”
BackgroundHegedűs, P., & Ferenć, R. (2022) · IEEE Access · doi:10.1109/access.2022.3176865 · Cited by 12
Piskachev, G., Becker, M., & Bodden, E. (2023) · Empirical Software Engineering · doi:10.1007/s10664-023-10354-3 · Cited by 11
“Similar results were reported also in the study by (Johnson et al., 2013), in which they performed semi-structured interviews with 16 developers from a single company and four graduate students.”
Rantala, L., Mäntylä, M., & Lenarduzzi, V. (2023) · Software Quality Journal · doi:10.1007/s11219-023-09655-z · Cited by 16
“Noise is one of the reasons developers dislike using static analysis tools, e.g., for bug hunting (Johnson et al., 2013).”
BackgroundInvestigating Controller Evolution and Divergence through Mining and Mutation
Balasubramaniam, B., Bagheri, H., Elbaum, S. G., & Bradley, J. M. (2020) · ACM/IEEE International Conference on Cyber-Physical Systems (ICCPS) · doi:10.1109/iccps48487.2020.00022 · Cited by 15
“But unless the annotation process is less costly, the sources of unsoundness controlled, and the tools well integrated into the developer’s environment and workflow, such strategies will struggle to gain mainstream acceptance [13], [14].”
MethodOn the Evolution of Inheritance and Delegation Mechanisms and Their Impact on Code Quality
Giordano, G., Fasulo, A., Catolino, G., Palomba, F., Ferrucci, F., & Gravino, C. (2022) · IEEE International Conference on Software Analysis, Evolution and Reengineering (SANER) · doi:10.1109/saner53432.2022.00113 · Cited by 13
Learning to Locate and Describe Vulnerabilities
Zhang, J., Liu, S., Wang, X., Li, T., & Liu, Y. (2023) · IEEE/ACM International Conference on Automated Software Engineering (ASE) · doi:10.1109/ase56229.2023.00045 · Cited by 16
Ostberg, J.-P., & Wagner, S. (2016) · IEEE International Conference on Software Analysis, Evolution and Reengineering (SANER) · doi:10.1109/saner.2016.63 · Cited by 13
Toward effective adoption of secure software development practices
Al‐Amin, S., Ajmeri, N., Du, H., Berglund, E. Z., & Singh, M. P. (2018) · Simulation Modelling Practice and Theory · doi:10.1016/j.simpat.2018.03.006 · Cited by 19
“Secure software development tools, or security tools, are programs that analyze software to help developers find and fix vulnerabilities [1, 2].”
Visual Analysis of Collective Anomalies Through High-Order Correlation Graph
Tao, J., Shi, L., Zhuang, Z., Huang, C., Yu, R., Su, P., Wang, C., & Chen, Y. (2018) · IEEE Pacific Visualization Symposium · doi:10.1109/pacificvis.2018.00027 · Cited by 11
“The traditional software analysis is based on the source code inspection [13, 25, 31] because the runtime analytics of software can evolve billions of executions per second and generate a huge volume of monitoring data.”
MethodA bug finder refined by a large set of open-source projects
Nam, J., Wang, S., Yuan, X., & Tan, L. (2019) · Information and Software Technology · doi:10.1016/j.infsof.2019.04.014 · Cited by 13
Team discussions and dynamics during DevOps tool adoptions in OSS projects
Yin, L., & Filkov, V. (2020) · IEEE/ACM International Conference on Automated Software Engineering (ASE) · doi:10.1145/3324884.3416640 · Cited by 14
“[21] consider that having intuitive defect presentation may contribute to the willingness of using static analysis tools.”
BackgroundSporq: An Interactive Environment for Exploring Code using Query-by-Example
Naik, A., Mendelson, J., Sands, N., Wang, Y., Naik, M., & Raghothaman, M. (2021) · ACM Symposium on User Interface Software and Technology (UIST) · doi:10.1145/3472749.3474737 · Cited by 16
Huang, Z., Shao, Z., Fan, G., Yu, H., Yang, X., & Yang, K. (2022) · Journal of Computer Science and Technology · doi:10.1007/s11390-021-1596-1 · Cited by 11
“quently, the outputs of SQA tools in purely technical aspects are perceived as unhelpful by practitioners [2]”
BackgroundUser interface design smell: Automatic detection and refactoring of Blob listeners
Blouin, A., Lelli, V., Baudry, B., & Coulon, F. (2018) · Information and Software Technology · doi:10.1016/j.infsof.2018.05.005 · Cited by 11
Evaluating and Integrating Diverse Bug Finders for Effective Program Analysis
Lu, B., Dong, W., Yin, L., & Zhang, L. (2018) · Lecture notes in computer science · doi:10.1007/978-3-030-04272-1_4 · Cited by 17
Comparative Analysis of Open-Source Tools for Conducting Static Code Analysis
Kuszczyński, K., & Walkowski, M. (2023) · Sensors · doi:10.3390/s23187978 · Cited by 10
“This generates numerous false positives, prolongs investigation time, and diminishes trust in SAST tool results [28].”
BackgroundSkalka, J., & Drlík, M. (2023) · IEEE Access · doi:10.1109/access.2023.3317694 · Cited by 19
“According to [14], current static analysis tools can provide developers with enough information to assess what to do with the warnings generated, but they rarely offer a relevant fix for what they claim is a problem.”
BackgroundSound and Partially-Complete Static Analysis of Data-Races in GPU Programs
Liew, D., Cogumbreiro, T., & Lange, J. (2024) · Proceedings of the ACM on Programming Languages · doi:10.1145/3689797 · Cited by 19
Combining Large Language Models with Static Analyzers for Code Review Generation
Jaoua, I., Sghaier, O. B., & Sahraoui, H. A. (2025) · International Conference on Mining Software Repositories (MSR) · doi:10.1109/msr66628.2025.00038 · Cited by 33
“Similarly, static analyzers, although reliable, may produce output overloaded with false positives [42], [43], making it difficult to separate significant concerns from noise.”
Analysis of Include Dependencies in C++ Source Code
Babati, B., & Pataki, N. (2017) · Annals of Computer Science and Information Systems · doi:10.15439/2017f358 · Cited by 10
“However, these tools are beneficial ones [8].”
An Empirical Study of Class Rebalancing Methods for Actionable Warning Identification
Ge, X., Fang, C., Bai, T., Liu, J., & Zhao, Z. (2023) · IEEE Transactions on Reliability · doi:10.1109/tr.2023.3234982 · Cited by 10
Finding Fixed Vulnerabilities with Off-the-Shelf Static Analysis
Dunlap, T., Thorn, S., Enck, W., & Reaves, B. (2023) · IEEE European Symposium on Security and Privacy · doi:10.1109/eurosp57164.2023.00036 · Cited by 10
“SAST tools are well-known to produce false positives [25], [52], [8].”
BackgroundHypothesizer: A Hypothesis-Based Debugger to Find and Test Debugging Hypotheses
Alaboudi, A., & LaToza, T. D. (2023) · ACM Symposium on User Interface Software and Technology (UIST) · doi:10.1145/3586183.3606781 · Cited by 20
Automating Static Code Analysis Through CI/CD Pipeline Integration
Wadhams, Z., Reinhold, A. M., & Izurieta, C. I. (2024) · IEEE International Conference on Software Analysis, Evolution and Reengineering - Companion (SANER-C) · doi:10.1109/saner-c62648.2024.00021 · Cited by 10
Active Documentation: Helping Developers Follow Design Decisions
Mehrpour, S., LaToza, T. D., & Kindi, R. K. (2019) · IEEE Symposium on Visual Languages and Human-Centric Computing (VL/HCC) · doi:10.1109/vlhcc.2019.8818816 · Cited by 15
ChangeViz: Enhancing the GitHub Pull Request Interface with Method Call Information
Gasparini, L., Fregnan, E., Braz, L., Baum, T., & Bacchelli, A. (2021) · IEEE Working Conference on Software Visualization (VISSOFT) · doi:10.1109/vissoft52517.2021.00022 · Cited by 15
An empirical study of Android behavioural code smells detection
Prestat, D., Moha, N., & Villemaire, R. (2022) · Empirical Software Engineering · doi:10.1007/s10664-022-10212-8 · Cited by 10
“Moreover, Johnson et al. (2013) conducted 20 interviews to understand the lack of interests from developers to use static analysis tools to find bugs.”
BackgroundImproving Review of Clustered-Code Analysis Warnings
Muske, T. (2014) · IEEE International Conference on Software Maintenance (ICSM) · doi:10.1109/icsme.2014.97 · Cited by 10
“Many times the involved efforts in reviewing the warnings have been found to be a reason for skipping the review process [7], and sometimes the reason to avoid usage of the static analysis tools [8].”
BackgroundMachine Learning based Static Code Analysis for Software Quality Assurance
Sultanow, E. G., Ullrich, A., Konopik, S., & Vladova, G. (2018) · International Conference on Digital Information Management · doi:10.1109/icdim.2018.8847079 · Cited by 10
Hassan, S. A., Aamir, Z., Lee, D., Davis, J. C., & Servant, F. (2023) · IEEE Symposium on Security and Privacy (S&P) · doi:10.1109/sp46215.2023.10179442 · Cited by 9
“We compared our anti-patterns to the state-of-the-art ones in a human-subjects experiment, simulating a context in which developers often prefer manual techniques [31], e.g., when tools disrupt developer workflow, such as in regex composition or when working with simple regexes (§8).”
BackgroundMethodInfluentialAugmented testing to support manual GUI-based regression testing: An empirical study
Bauer, A., Frattini, J., & Alégroth, E. (2024) · Empirical Software Engineering · doi:10.1007/s10664-024-10522-z · Cited by 11
Barriers to Using Static Application Security Testing (SAST) Tools: A Literature Review
Wadhams, Z., Izurieta, C. I., & Reinhold, A. M. (2024) · IEEE/ACM International Conference on Automated Software Engineering Workshops (ASEW) · doi:10.1145/3691621.3694947 · Cited by 9
“While implementing SAST is relatively easy and has shown benefits, some development teams still choose not to use it, opting for limited code analysis, focusing on security-critical components only, or relying mostly on manual code reviews [11, 16, 30].”
Trautsch, A., Herbold, S., & Grabowski, J. (2023) · Empirical Software Engineering · doi:10.1007/s10664-023-10301-2 · Cited by 9
“However, due to their rule matching nature, ASATs are prone to false positives, i.e., warnings about code that is not problematic (Johnson et al. 2013).”
BackgroundA Usability Evaluation of AFL and libFuzzer with CS Students
Plöger, S., Meier, M., & Smith, M. (2023) · CHI Conference on Human Factors in Computing Systems · doi:10.1145/3544548.3581178 · Cited by 10
How do Developers Improve Code Readability? An Empirical Study of Pull Requests
Dantas, C. E. C., Rocha, A. M., & Maia, M. D. A. (2023) · IEEE International Conference on Software Maintenance (ICSM) · doi:10.1109/icsme58846.2023.00022 · Cited by 21
“ASATs help to reveal coding rule violations as warnings during the development process, allowing developers to correct them before they are released as part of the software, thus ensuring a higher quality of software during the development process [32].”
BackgroundCheetah: just-in-time taint analysis for android apps
Quang, L. N., Ali, K., Livshits, B., Bodden, E., Smith, J., & Murphy-Hill, E. R. (2017) · ACM/IEEE International Conference on Software Engineering: Companion Proceedings (ICSE-Companion) · doi:10.1109/icse-c.2017.20 · Cited by 9
“However, most developers do not use static-analysis tools, because they generate many false positives and may take hours, or even days, to run on sizeable code bases [1], [2].”
BackgroundMethodSelf-citationLight-Touch Interventions to Improve Software Development Security
Weir, C., Blair, L., Becker, I., Sasse, M. A., & Noble, J. (2018) · IEEE Cybersecurity Development (SecDev) · doi:10.1109/secdev.2018.00019 · Cited by 13
“A survey by Johnson et al. analyzed ‘Why Don’t Software Developers Use Static Analysis Tools to Find Bugs’ [8] and produced a set of recommendations for tool functionality; in particular the ability to avoid repeated false positives and support for ‘quick fixes’.”
BackgroundWorrisome Patterns in Developers: A Survey in Cryptography
Hazhirpasand, M., & Ghafari, M. (2021) · IEEE/ACM International Conference on Automated Software Engineering Workshops (ASEW) · doi:10.1109/asew52652.2021.00045 · Cited by 9
Mokhberi, A., & Beznosov, K. (2021) · European Symposium on Usable Security (EuroUSEC) · doi:10.1145/3481357.3481522 · Cited by 9
“to go outside of a code development environment to use a tool or see the tool’s results [44], tools’ interface complexity [96], perceived uselessness of tools, and lack of awareness of the tools [10].”
BackgroundMethodInfluentialGerasimov, A. Y., Kruglov, L. V., Ermakov, M. K., & Vartanov, S. P. (2018) · Programming and Computer Software · doi:10.1134/s0361768818060051 · Cited by 9
“It should be noted that static analysis methods are not sufficiently accurate in bug detection [6, 7], which is primarily due to the scalability and performance requirements for static analysis [8, 9].”
BackgroundKim, T., Park, S., & Kim, H. (2023) · International Symposium on Research in Attacks, Intrusions and Defenses (RAID) · doi:10.1145/3607199.3607244 · Cited by 11
“[22] conducted a user study with 20 developers to determine why software developers do not use static analysis tools for bug detection.”
BackgroundAnalyzing source code vulnerabilities in the D2A dataset with ML ensembles and C-BERT
Pujar, S., Zheng, Y., Buratti, L., Lewis, B. L., Chen, Y. Q., Laredo, J., Morari, A., Epstein, E., Lin, T.-N., Yang, B. S., et al. (2024) · Empirical Software Engineering · doi:10.1007/s10664-023-10405-9 · Cited by 12
Using Semgrep OSS to Find OWASP Top 10 Weaknesses in PHP Applications: A Case Study
Kree, L., Helmke, R., & Winter, E. (2024) · Lecture notes in computer science · doi:10.1007/978-3-031-64171-8_4 · Cited by 15
Kushigian, B., Kaufman, S. J., Featherman, R., Potter, H., Madadi, A., & Just, R. (2024) · ACM SIGSOFT International Symposium on Software Testing and Analysis (ISSTA) · doi:10.1145/3650212.3680310 · Cited by 8
Vulnerability Classification on Source Code Using Text Mining and Deep Learning Techniques
Kalouptsoglou, I., Siavvas, M., Ampatzoglou, A., Kehagias, D. D., & Chatzigeorgiou, A. (2024) · IEEE International Conference on Software Quality, Reliability and Security Companion (QRS-C) · doi:10.1109/qrs-c63300.2024.00017 · Cited by 8
“…being able to identify not only coding violations of pre-defined rules but also complex vulnerability patterns that cannot be expressed in the form of static analysis rules [13][14], it lacks the ability of static code analyzers to present specific lines and categories of the security alerts [15].”
BackgroundSteenhoek, B. J., Sivaraman, K., Gonzalez, R. S., Mohylevskyy, Y., Moghaddam, R. Z., & Le, W. (2025) · ACM/IEEE International Conference on Software Engineering: Companion Proceedings (ICSE-Companion) · doi:10.1109/icse55347.2025.00126 · Cited by 28
“User studies of static analysis and AI tools: We developed our tool based on findings and recommendations from several user studies of traditional static analysis tools [15, 27, 46] (see Section II-A for more details).”
InfluentialTo Fix or Not to Fix: A Critical Study of Crypto-misuses in the Wild
Wickert, A.-K., Baumgärtner, L., Schlichtig, M., Narasimhan, K., & Mezini, M. (2022) · IEEE International Conference on Trust, Security and Privacy in Computing and Communications (TrustCom) · doi:10.1109/trustcom56396.2022.00051 · Cited by 14
“Past research has shown that developers consider false positives as the "Achilles heel" of static analyzes [11], [2].”
BackgroundStochastic actor-oriented modeling for studying homophily and social influence in OSS projects
Kavaler, D., & Filkov, V. (2016) · Empirical Software Engineering · doi:10.1007/s10664-016-9431-y · Cited by 9
“, are not clearly associated to developer actions, as demonstrated by the challenge they present in identifying (Johnson et al. 2013).”
BackgroundData-Driven Insights from Vulnerability Discovery Metrics
Munaiah, N., & Meneely, A. (2019) · doi:10.1109/rcose/ddree.2019.00008 · Cited by 10
Reducing Static Analysis Alarms Based on Non-impacting Control Dependencies
Muske, T., Talluri, R., & Serebrenik, A. (2019) · Lecture notes in computer science · doi:10.1007/978-3-030-34175-6_7 · Cited by 8
Exploring software reusability metrics with Q&A forum data
Patrick, M. T. (2020) · Journal of Systems and Software · doi:10.1016/j.jss.2020.110652 · Cited by 9
“[51] suggested it is underused in practice, due to problems with false positives.”
BackgroundComparing Different Developer Behavior Recommendation Styles
Brown, C., & Parnin, C. (2020) · International Conference on Software Engineering · doi:10.1145/3387940.3391481 · Cited by 12
“We observed tool recommendations because, while studies shows static analysis tool usage is beneficial for software engineering teams, research also suggests developers rarely use them in practice [24].”
MethodInfERL: scalable and extensible Erlang static analysis
Hajdu, Á., Marescotti, M., Suzanne, T., Mao, K., Grigore, R., Gustafsson, P., & Distefano, D. (2022) · ACM SIGPLAN Workshop on Erlang (Erlang) · doi:10.1145/3546186.3549929 · Cited by 8
“One widely reported challenge of deploying static analyzers at scale in industry is the potential high false positive (false alarm) rate of reported issues [7, 11].”
BackgroundAn unsupervised feature selection approach for actionable warning identification
Ge, X., Fang, C., Liu, J., Qing, M., Li, X., & Zhao, Z. (2023) · Expert Systems with Applications · doi:10.1016/j.eswa.2023.120152 · Cited by 8
How software users recommend tools to each other
Brown, C., Middleton, J., Sharma, E., & Murphy-Hill, E. R. (2017) · IEEE Symposium on Visual Languages and Human-Centric Computing (VL/HCC) · doi:10.1109/vlhcc.2017.8103460 · Cited by 9
Self-citationA Dataset of Parametric Cryptographic Misuses
Wickert, A.-K., Reif, M., Eichberg, M., Dodhy, A., & Mezini, M. (2019) · International Conference on Mining Software Repositories (MSR) · doi:10.1109/msr.2019.00023 · Cited by 11
“Our analysis reveals that Find Security Bugs is usable in practice [15] due to a precision of 100%.”
BackgroundIDE support for cloud-based static analyses
Luo, L., Schäf, M., Sanchez, D., & Bodden, E. (2021) · ACM Joint European Software Engineering Conference and Symposium on the Foundations of Software Engineering (ESEC/FSE) · doi:10.1145/3468264.3468535 · Cited by 11
“interviewed experienced developers to understand why developers were not widely using static analysis tools [16].”
BackgroundRanking Warnings of Static Analysis Tools Using Representation Learning
Ngo, K.-T., Do, D.-T., Nguyen, T.-T., & Vo, H. D. (2021) · Asia-Pacific Software Engineering Conference (APSEC) · doi:10.1109/apsec53868.2021.00040 · Cited by 13
Position: Vibe Coding Needs Vibe Reasoning: Improving Vibe Coding with Formal Verification
Mitchell, J., & Shaaban, Y. (2025) · Proceedings of the 1st ACM SIGPLAN International Workshop on Language Models and Programming Languages · doi:10.1145/3759425.3763390 · Cited by 8
The Impact of Shift-Left Testing to Software Quality in Agile Methodology: A Case Study
Andriadi, K., Soeparno, H., Gaol, F. L., & Arifin, Y. (2023) · International Conference on Information Management and Technology (ICIMTech) · doi:10.1109/icimtech59029.2023.10277919 · Cited by 7
“Another way to reduce bugs is using static tools that scan the project [15], but there is a possibility that the tools give the wrong result, something like the code that should be good but is marked as bugs or vice versa.”
BackgroundDevelopers' Approaches to Software Supply Chain Security: An Interview Study
Sammak, R., Rotthaler, A. L., Ramulu, H. S., Wermke, D., & Acar, Y. (2023) · ACM Workshop on Software Supply Chain Offensive Research and Ecosystem Defenses (SCORED) · doi:10.1145/3689944.3696160 · Cited by 21
“Past studies also covered individual SSC technology topics such as open source components [69, 70], development processes and tooling [25, 29], programming languages [27], cryptography and authentication [16, 26, 32], reproducible builds [17], and dependency selection [39, 55].”
Shen, M., Pillai, A. A., Yuan, B. A., Davis, J. C., & Machiry, A. (2025) · Proceedings of the ACM on software engineering. · doi:10.1145/3728923 · Cited by 14
“We therefore adopted the Full Disclosure approach by opening public issues or pull requests with patches for the identified vulnerabilities, as detailed in §5.2.4.”
InfluentialFrom Leaks to Fixes: Automated Repairs for Resource Leak Warnings
Utture, A., & Palsberg, J. (2023) · ACM Joint European Software Engineering Conference and Symposium on the Foundations of Software Engineering (ESEC/FSE) · doi:10.1145/3611643.3616267 · Cited by 13
“Other developer studies [20, 31, 53] also report very similar findings.”
ResultUnderstanding and Detecting Annotation-Induced Faults of Static Analyzers
Zhang, H., Pei, Y., Liang, S., & Tan, S. H. (2024) · Proceedings of the ACM on software engineering. · doi:10.1145/3643759 · Cited by 7
“In this section, we describe the four symptoms and then relate them to the six root causes to help users and developers assess the impacts of different root causes.”
A Method for Finding Missing Unit Tests
Gaston, D., & Clause, J. (2020) · IEEE International Conference on Software Maintenance (ICSM) · doi:10.1109/icsme46990.2020.00019 · Cited by 7
“, erroneous reports) are one of the main reasons that developers abandon static analysis tools [27].”
BackgroundInvestigating the impact of vulnerability datasets on deep learning-based vulnerability detectors
Liu, L., Li, Z., Wen, Y., & Chen, P. (2022) · PeerJ Computer Science · doi:10.7717/peerj-cs.975 · Cited by 7
“Code similarity-based methods have a high rate of false positives and false negatives (Johnson et al., 2013).”
BackgroundFluently specifying taint-flow queries with fluentTQL
Piskachev, G., Späth, J., Budde, I., & Bodden, E. (2022) · Empirical Software Engineering · doi:10.1007/s10664-022-10165-y · Cited by 13
“Empirical studies show that software developers need static analysis tools integrated in their workflow (Christakis and Bird, 2016; Johnson et al., 2013).”
BackgroundA systematic mapping study of bug reproduction and localization
Wang, D., Galster, M., & Morales-Trujillo, M. E. (2023) · Information and Software Technology · doi:10.1016/j.infsof.2023.107338 · Cited by 13
Pistoia, M., Tripp, O., & Lubensky, D. M. (2016) · Advances in multimedia and interactive technologies book series · doi:10.4018/978-1-5225-0945-5.ch004 · Cited by 8
Recommending source code locations for system specific transformations
Santos, G., Paixão, K. V. R., Anquetil, N., Etien, A., Maia, M. D. A., & Ducasse, S. (2017) · IEEE International Conference on Software Analysis, Evolution and Reengineering (SANER) · doi:10.1109/saner.2017.7884618 · Cited by 7
Examination of Coding Violations Focusing on Their Change Patterns over Releases
Burhandenny, A. E., Aman, H., & Kawahara, M. (2016) · Asia-Pacific Software Engineering Conference (APSEC) · doi:10.1109/apsec.2016.027 · Cited by 7
Test Tools: an illusion of usability?
Evans, I., Porter, C., Micallef, M. J., & Harty, J. (2020) · IEEE International Conference on Software Testing, Verification and Validation Workshops (ICSTW) · doi:10.1109/icstw50294.2020.00070 · Cited by 7
“Work examining programmers’ use of static analysis tools [19], uncovered usability challenges, for example, one participant in that study says: “... none of these [messages from the tool] really help me” .”
BackgroundUser-Centered Design of Visualizations for Software Vulnerability Reports
Reynolds, S. L., Mertz, T., Arzt, S., & Kohlhammer, J. (2021) · IEEE Symposium on Visualization for Cyber Security (VIZSEC) · doi:10.1109/vizsec53666.2021.00013 · Cited by 7
“One frequently criticized issue of static analysis tools is the number of false positives [18].”
BackgroundStray, V. G., Stol, K.-J., Paasivaara, M., & Kruchten, P. B. (2022) · Lecture notes in business information processing · doi:10.1007/978-3-031-08169-9 · Cited by 10
Executable Counterexamples in Software Model Checking
Gennari, J., Gurfinkel, A., Kahsai, T., Navas, J. A., & Schwartz, E. J. (2018) · Lecture notes in computer science · doi:10.1007/978-3-030-03592-1_2 · Cited by 7
Harnessing the Power of LLMs: LLM Summarization for Human-Centric DAST Reports
Thool, A., & Brown, C. (2024) · IEEE Symposium on Visual Languages and Human-Centric Computing (VL/HCC) · doi:10.1109/vl/hcc60511.2024.00014 · Cited by 12
“For instance, prior work shows the lack of understandable and customizable output prevents developers from adopting static analysis tools [56] and fixing security issues [57].”
BackgroundOn the correlation between architectural smells and static analysis warnings
Esposito, M., Robredo, M., Fontana, F. A., & Lenarduzzi, V. (2025) · Software Quality Journal · doi:10.1007/s11219-025-09730-7 · Cited by 10
The impact of hard and easy negative training data on vulnerability prediction performance
Debeyan, F. A., Madeyski, L., Hall, T., & Bowes, D. (2024) · Journal of Systems and Software · doi:10.1016/j.jss.2024.112003 · Cited by 6
sqlFuzz: Directed Fuzzing for SQL Injection Vulnerability
Yuan, Y., Lu, Y., Zhu, K.-L., Huang, H., Chen, Y., & Zhang, Y. (2024) · Electronics · doi:10.3390/electronics13152946 · Cited by 6
Requirements Engineering for Trustworthy Human-AI Synergy in Software Engineering 2.0
Lo, D. (2024) · IEEE International Requirements Engineering Conference (RE) · doi:10.1109/re59067.2024.00011 · Cited by 7
Jerónimo, A. H., Moreno, P. M., Camacho, J. A. V., & Vega, G. C. (2024) · IEEE International Conference on Engineering Veracruz (ICEV) · doi:10.1109/icev63254.2024.10766004 · Cited by 6
SARIF-Enabled Tooling to Encourage Gradual Technical Debt Reduction
Anderson, P., Kot, Ł., Gilmore, N., & Vitek, D. (2019) · IEEE/ACM International Conference on Technical Debt (TechDebt) · doi:10.1109/techdebt.2019.00024 · Cited by 6
“Even apparently small barriers to their usage can hinder their usage significantly, a finding that has been confirmed independently multiple times [4, 5].”
BackgroundFast and precise application code analysis using a partial library
Utture, A., & Palsberg, J. (2022) · ACM/IEEE International Conference on Software Engineering: Companion Proceedings (ICSE-Companion) · doi:10.1145/3510003.3510046 · Cited by 6
“Other empirical studies [4, 13] also arrive at similar conclusions.”
ResultImproving Assessment of Programming Pattern Knowledge through Code Editing and Revision
Nurollahian, S., Rafferty, A. N., & Wiese, E. S. (2023) · IEEE/ACM International Conference on Software Engineering: Software Engineering Education and Training (ICSE-SEET) · doi:10.1109/icse-seet58685.2023.00012 · Cited by 6
“The messages from these analyzers are difficult to interpret and act on, both for students [25] and also for professional software developers [26], [27].”
BackgroundResolving Security Issues via Quality-Oriented Refactoring: A User Study
Gigante, D., Pecorelli, F., Barletta, V. S., Janes, A., Lenarduzzi, V., Taibi, D., & Baldassarre, M. T. (2023) · IEEE/ACM International Conference on Technical Debt (TechDebt) · doi:10.1109/techdebt59074.2023.00016 · Cited by 6
The Effectiveness of Security Interventions on GitHub
Fischer, F., Höbenreich, J., & Großklags, J. (2023) · ACM SIGSAC Conference on Computer and Communications Security (CCS) · doi:10.1145/3576915.3623174 · Cited by 11
Tracking the Evolution of Static Code Warnings: The State-of-the-Art and a Better Approach
Li, J., & Yang, J. (2024) · IEEE Transactions on Software Engineering · doi:10.1109/tse.2024.3358283 · Cited by 6
Reducing False Positives of Static Bug Detectors Through Code Representation Learning
Yang, Y., Wen, M., Gao, X. Y., Zhang, Y., & Sun, H. (2024) · IEEE International Conference on Software Analysis, Evolution and Reengineering (SANER) · doi:10.1109/saner60148.2024.00075 · Cited by 12
Marea: A Semi-Automatic Decision Support System for Breaking Dependency Cycles
Caracciolo, A., Aga, B., Lungu, M. F., & Nierstrasz, O. (2016) · IEEE International Conference on Software Analysis, Evolution and Reengineering (SANER) · doi:10.1109/saner.2016.11 · Cited by 6
“com/products/sonargraph appreciated by developers [9], [10].”
RulePad: interactive authoring of checkable design rules
Mehrpour, S., LaToza, T. D., & Sarvari, H. (2020) · ACM Joint European Software Engineering Conference and Symposium on the Foundations of Software Engineering (ESEC/FSE) · doi:10.1145/3368089.3409751 · Cited by 8
“rking with program analysis tools as well as offered approaches to mitigate those issues. Developers face a number of barriers that can lead to misuse of the tools and discourage them from using them [6, 16]. These include a high number of false positives, poor organization of warnings, lack of support for collaborati…”
BackgroundDemystifying “bad” error messages in data science libraries
Tao, Y., Chen, Z., Liu, Y., Xuan, J., Xu, Z., & Qin, S. (2021) · ACM Joint European Software Engineering Conference and Symposium on the Foundations of Software Engineering (ESEC/FSE) · doi:10.1145/3468264.3468560 · Cited by 6
“While previous work mostly addressed the quality of error messages generated by compilers [3][4][34], system software [36][39], and static analysis tools [2][20], limited knowledge is available about this issue in the domain of data science.”
BackgroundWalls, Pillars and Beams: A 3D Decomposition of Quality Anomalies
Tymchuk, Y., Merino, L., Ghafari, M., & Nierstrasz, O. (2016) · IEEE Working Conference on Software Visualization (VISSOFT) · doi:10.1109/vissoft.2016.9 · Cited by 8
“I. Introduction As a software system evolves, its architecture tends to erode, making it harder to understand, change, test and debug [1].”
BackgroundAnalyzing the Decision Criteria of Software Developers Based on Prospect Theory
Kina, K., Tsunoda, M., Hata, H., Tamada, H., & Igaki, H. (2016) · IEEE International Conference on Software Analysis, Evolution and Reengineering (SANER) · doi:10.1109/saner.2016.115 · Cited by 7
Cyber Resilient Flight Software for Spacecraft
Wheeler, W. A., Cohen, N., Betser, J., Meyers, C., Snavely, W., Chaki, S., Riley, M., & Runyon, B. (2017) · AIAA SPACE and Astronautics Forum and Exposition · doi:10.2514/6.2017-5305 · Cited by 6
A hybrid approach to improving program security
Nembhard, F., Carvalho, M., & Eskridge, T. C. (2017) · IEEE Symposium Series on Computational Intelligence (SSCI) · doi:10.1109/ssci.2017.8285247 · Cited by 8
“Additionally, static analysis tools often report lengthy and numerous alerts, which cause a lack of acceptance by developers and businesses [11], [21].”
BackgroundAn Empirical Study of Suppressed Static Analysis Warnings
Hu, H., Wang, Y., Rubin, J., & Pradel, M. (2025) · Proceedings of the ACM on software engineering. · doi:10.1145/3715729 · Cited by 5
“Unfortunately, not all warnings reported by a static analyzer are immediately useful to developers [28, 42], e.g., because a warning is a false positive or the developers do not consider it important enough to address.”
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.