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 101–200 of 567
An Evolutionary Study of Configuration Design and Implementation in Cloud Systems
Zhang, Y., He, H., Legunsen, O., Li, S., Dong, W., & Xu, T. (2021) · ACM/IEEE International Conference on Software Engineering: Companion Proceedings (ICSE-Companion) · doi:10.1109/icse43902.2021.00029 · Cited by 43
Studying Duplicate Logging Statements and Their Relationships With Code Clones
Li, Z., Chen, T.-H. P., Yang, J., & Shang, W. (2021) · IEEE Transactions on Software Engineering · doi:10.1109/tse.2021.3060918 · Cited by 38
“Similar to some code smells studied in prior research [44], [45], developers may be reluctant to fix DP due to additional maintenance overheads but limited supports (i.”
ResultActive Learning of Discriminative Subgraph Patterns for API Misuse Detection
Kang, H. J., & Lo, D. (2021) · IEEE Transactions on Software Engineering · doi:10.1109/tse.2021.3069978 · Cited by 36
Test mimicry to assess the exploitability of library vulnerabilities
Kang, H. J., Nguyen, T. G., Le, B., Păsăreanu, C. S., & Lo, D. (2022) · ACM SIGSOFT International Symposium on Software Testing and Analysis (ISSTA) · doi:10.1145/3533767.3534398 · Cited by 27
“We propose test mimicry to leverage vulnerability-witnessing test cases from open-source libraries, generating test cases for client projects that demonstrate the exploitability of the library vulnerabilities.”
MethodDo I really need all this work to find vulnerabilities?
Elder, S., Zahan, N., Shu, R., Metro, M., Kozarev, V., Menzies, T., & Williams, L. A. (2022) · Empirical Software Engineering · doi:10.1007/s10664-022-10179-6 · Cited by 36
“SAST tools are a common way to comprehensively apply source code analysis, as manual source code analysis can be tedious and time-consuming [54, 43, 87, 91, 20].”
BackgroundMethodExplaining Software Bugs Leveraging Code Structures in Neural Machine Translation
Mahbub, P., Shuvo, O., & Rahman, M. M. (2023) · ACM/IEEE International Conference on Software Engineering: Companion Proceedings (ICSE-Companion) · doi:10.1109/icse48619.2023.00063 · Cited by 44
Static Analysis of JavaScript Web Applications in the Wild via Practical DOM Modeling (T)
Park, C., Won, S., Jin, J., & Ryu, S. (2015) · IEEE/ACM International Conference on Automated Software Engineering (ASE) · doi:10.1109/ase.2015.27 · Cited by 26
Applying Mutation Analysis on Kernel Test Suites: An Experience Report
Ahmed, I., Jensen, C., Groce, A., & McKenney, P. E. (2017) · IEEE International Conference on Software Testing, Verification and Validation Workshops (ICSTW) · doi:10.1109/icstw.2017.26 · Cited by 26
“Source code analysis generates a large number of false positives and warnings [20] which need to be screened by domain experts, which is expensive in terms of both time and resources.”
BackgroundOn Reducing the Energy Consumption of Software: From Hurdles to Requirements
Ournani, Z., Rouvoy, R., Rust, P., & Penhoat, J. (2020) · Proceedings of the ... ACM-IEEE International Symposium on Empirical Software Engineering and Measurement/International Symposium on Empirical Software Engineering and Measurement · doi:10.1145/3382494.3410678 · Cited by 50
“work [15], in which they interviewed 20 candidates through a qualitative study and discussed why developers do not use static analysis to find bugs,”
BackgroundUnderstanding static code warnings: An incremental AI approach
Yang, X., Yu, Z., Wang, J., & Menzies, T. (2020) · Expert Systems with Applications · doi:10.1016/j.eswa.2020.114134 · Cited by 35
“Previous studies have shown that false positives in static alerts have been one of the most important barriers for developers to use static analysis tools (Avgustinov et al., 2015; Johnson et al., 2013; Thung et al., 2015).”
BackgroundHERMES: Using Commit-Issue Linking to Detect Vulnerability-Fixing Commits
Nguyen-Truong, G., Kang, H. J., Lo, D., Sharma, A., Santosa, A. E., Sharma, A., & Ang, M. Y. (2022) · IEEE International Conference on Software Analysis, Evolution and Reengineering (SANER) · doi:10.1109/saner53432.2022.00018 · Cited by 26
Barik, T., Song, Y., Johnson, B., & Murphy-Hill, E. R. (2016) · IEEE International Conference on Software Maintenance (ICSM) · doi:10.1109/icsme.2016.63 · Cited by 35
“Our analytic evaluation method with six usability experts identified trade-offs between FIXBUGS and Quick Fix, and suggests ways in which FIXBUGS and Quick Fix can offer complementary capabilities to better support developers.”
MethodSelf-citationTop Score on the Wrong Exam: On Benchmarking in Machine Learning for Vulnerability Detection
Risse, N., Liu, J., & Böhme, M. (2025) · Proceedings of the ACM on software engineering. · doi:10.1145/3728887 · Cited by 94
“2) Datasets: Which datasets do they use to evaluate their techniques empirically?”
A transformer-based IDE plugin for vulnerability detection
Mamede, C., Pinconschi, E., & Abreu, R. (2022) · IEEE/ACM International Conference on Automated Software Engineering (ASE) · doi:10.1145/3551349.3559534 · Cited by 35
“These include poorly presented outputs, a lack of actionable solutions for detected vulnerabilities, and too much noise between the alerts and what is relevant [9, 15].”
BackgroundExplaining Static Analysis - A Perspective
Nachtigall, M., Quang, L. N., & Bodden, E. (2019) · IEEE/ACM International Conference on Automated Software Engineering Workshops (ASEW) · doi:10.1109/asew.2019.00023 · Cited by 45
Sönmez, F. Ö., & Günel, B. (2021) · IEEE Access · doi:10.1109/access.2021.3057044 · Cited by 24
Navigate, Understand, Communicate: How Developers Locate Performance Bugs
Baltes, S., Moseler, O., Beck, F., & Diehl, S. (2015) · Proceedings of the ... ACM-IEEE International Symposium on Empirical Software Engineering and Measurement/International Symposium on Empirical Software Engineering and Measurement · doi:10.1109/esem.2015.7321208 · Cited by 27
Towards the application of recommender systems to secure coding
Nembhard, F., Carvalho, M., & Eskridge, T. C. (2019) · EURASIP Journal on Information Security · doi:10.1186/s13635-019-0092-4 · Cited by 31
Sorald: Automatic Patch Suggestions for SonarQube Static Analysis Violations
Etemadi, K., Harrand, N., Larsén, S., Adzemovic, H., Phu, H. L., Verma, A., Madeiral, F., Wikström, D., & Monperrus, M. (2022) · IEEE Transactions on Dependable and Secure Computing · doi:10.1109/tdsc.2022.3167316 · Cited by 40
ROSDiscover: Statically Detecting Run-Time Architecture Misconfigurations in Robotics Systems
Timperley, C. S., Dürschmid, T., Schmerl, B. R., Garlan, D., & Goues, C. L. (2022) · IEEE International Conference on Software Architecture (ICSA) · doi:10.1109/icsa53651.2022.00019 · Cited by 23
“The main challenge of bug detection is to define rules that find useful errors while minimizing false positives [23], [24].”
An Extensive Comparison of Static Application Security Testing Tools
Esposito, M., Falaschi, V., & Falessi, D. (2024) · International Conference on Evaluation and Assessment in Software Engineering (EASE) · doi:10.1145/3661167.3661199 · Cited by 46
“Our evaluation of SASTTs features the following novelties over previous SASTTs evaluations [2, 4, 12, 15, 25–27, 31, 33, 38, 42, 47, 49, 51, 53, 62, 78–80] on JTS: • largest set of considered SASTTs, • largest set of considered CWEs, • analysis of uncovered CWEs and test cases, • actual vs expected…”
MethodInfluentialPorto, P. X. (. 2., Garbajosa, J., & Wang, X. (2018) · Lecture notes in business information processing · doi:10.1007/978-3-319-91602-6 · Cited by 35
Current Challenges in Practical Object-Oriented Software Design
Aniche, M. F., Yoder, J. W., & Kon, F. (2019) · IEEE/ACM International Conference on Software Engineering: New Ideas and Emerging Results (ICSE-NIER) · doi:10.1109/icse-nier.2019.00037 · Cited by 28
Assessing the Readability of ChatGPT Code Snippet Recommendations: A Comparative Study
Dantas, C., Rocha, A. M., & Maia, M. D. A. (2023) · Brazilian Symposium on Software Engineering · doi:10.1145/3613372.3613413 · Cited by 34
“As a result, they contribute to ensuring higher software quality during development [17].”
BackgroundStatic Analysis Toolset with Clang
Babati, B., Horväth, G., Májer, V., & Pataki, N. (2018) · International Conference on Applied Informatics (ICAI) · doi:10.14794/icai.10.2017.23 · Cited by 22
AID: An Automated Detector for Gender-Inclusivity Bugs in OSS Project Pages
Chatterjee, A., Guizani, M., Stevens, C., Emard, J., May, M. E., Burnett, M., & Ahmed, I. (2021) · ACM/IEEE International Conference on Software Engineering: Companion Proceedings (ICSE-Companion) · doi:10.1109/icse43902.2021.00128 · Cited by 27
“Since false positives play a critical role in developers’ dissatisfaction with current tools [52], A ID ’s precision, a measure of false positive rate, could be critical to its acceptance.”
BackgroundDo Static Analysis Tools Affect Software Quality when Using Test-driven Development?
Romano, S., Zampetti, F., Baldassarre, M. T., Penta, M. D., & Scanniello, G. (2022) · Proceedings of the ... ACM-IEEE International Symposium on Empirical Software Engineering and Measurement/International Symposium on Empirical Software Engineering and Measurement · doi:10.1145/3544902.3546233 · Cited by 31
“[29], by interviewing 20 developers shed light on the reasons why developers underuse SATs despite their benefits—i.”
BackgroundOn Combining Diverse Static Analysis Tools for Web Security: An Empirical Study
Nunes, P., Medeiros, I., Fonseca, J., Neves, N., Correia, M. P., & Vieira, M. P. A. (2017) · European Dependable Computing Conference · doi:10.1109/edcc.2017.16 · Cited by 22
Automated Discovery of Cross-Plane Event-Based Vulnerabilities in Software-Defined Networking
Ujcich, B. E., Jero, S., Skowyra, R., Gomez, S. R., Bates, A., Sanders, W. H., & Okhravi, H. (2020) · Network and Distributed System Security Symposium · doi:10.14722/ndss.2020.24080 · Cited by 27
AutoPruner: transformer-based call graph pruning
Le-Cong, T., Kang, H.-J., Nguyen, T.-G., Haryono, S. A., Lo, D., Le, X., & Huynh, Q.-T. (2022) · ESEC/SIGSOFT FSE · doi:10.1145/3540250.3549175 · Cited by 29
“would reduce the amount of developer effort spent inspecting false alarms, which is known to be a barrier to the adoption of bug detection tools based on static analysis [20].”
BackgroundRahman, A., & Parnin, C. (2023) · IEEE Transactions on Software Engineering · doi:10.1109/tse.2023.3265962 · Cited by 36
“Low precision static analysis tool contribute to a lack of actionability, which in turn results in abandonment of static analysis tool usage [10], [30], [37].”
BackgroundAlqaradaghi, M., & Kozsik, T. (2024) · IEEE Access · doi:10.1109/access.2024.3389955 · Cited by 21
“One of the main causes of static analysis tools’ perceived uselessness is their lack of precision [24].”
BackgroundTorunski, E., Shafiq, M. O., & Whitehead, A. D. (2017) · International Conference on Digital Information Management · doi:10.1109/icdim.2017.8244675 · Cited by 21
“[7] talked about the use of static code analysis tools.”
BackgroundContinuous Refactoring in CI: A Preliminary Study on the Perceived Advantages and Barriers
Vassallo, C., Palomba, F., & Gall, H. C. (2018) · IEEE International Conference on Software Maintenance (ICSM) · doi:10.1109/icsme.2018.00068 · Cited by 29
“However, static analysis tools still generate false alarms [10], preventing them from being fully trusted by developers.”
BackgroundUsing Machine Learning Techniques to Classify and Predict Static Code Analysis Tool Warnings
Alikhashashneh, E. A., Raje, R. R., & Hill, J. H. (2018) · IEEE/ACS International Conference on Computer Systems and Applications (AICCSA) · doi:10.1109/aiccsa.2018.8612819 · Cited by 28
Deep security analysis of program code: A systematic literature review
Sonnekalb, T., Heinze, T. S., & Mäder, P. (2021) · Empirical Software Engineering · doi:10.1007/s10664-021-10029-x · Cited by 30
“Furthermore, considering their statistical nature, DL methods also promise to cope better with the not well-defined characteristics of software vulnerabilities, which becomes apparent when considering the often reported high numbers of false positives for traditional program analysis (Johnson et al. 2013; Christakis a…”
BackgroundMethodHow to Find Actionable Static Analysis Warnings: A Case Study With FindBugs
Yedida, R., Kang, H. J., Tu, H., Yang, X., Lo, D., & Menzies, T. (2023) · IEEE Transactions on Software Engineering · doi:10.1109/tse.2023.3234206 · Cited by 33
“The large number of false alarms produced is a barrier to adoption [15], [27], [44], [55]; it is easy to imagine how developers will be frustrated by using tools that require them to inspect numerous false alarms before finding a real bug.”
BackgroundIncrementalizing Production CodeQL Analyses
Szabó, T. (2023) · ACM Joint European Software Engineering Conference and Symposium on the Foundations of Software Engineering (ESEC/FSE) · doi:10.1145/3611643.3613860 · Cited by 20
“29007/tbm7 [17] Brittany Johnson, Yoonki Song, Emerson Murphy-Hill, and Robert Bowdidge.”
BackgroundInfluentialValidating and prioritizing quality rules for managing technical debt: An industrial case study
Falessi, D., & Voegele, A. (2015) · IEEE/ACM International Conference on Technical Debt (TechDebt) · doi:10.1109/mtd.2015.7332623 · Cited by 35
“Moreover, we note that our “Very Low” level of interest could be close to what in other studies is referred as false positive [20] [21].”
ResultTransfer learning for software vulnerability prediction using Transformer models
Kalouptsoglou, I., Siavvas, M., Ampatzoglou, A., Kehagias, D. D., & Chatzigeorgiou, A. (2025) · Journal of Systems and Software · doi:10.1016/j.jss.2025.112448 · Cited by 28
Heard it through the Gitvine: an empirical study of tool diffusion across the npm ecosystem
Lamba, H., Trockman, A., Armanios, D. E., Kästner, C., Miller, H., & Vasilescu, B. (2020) · ACM Joint European Software Engineering Conference and Symposium on the Foundations of Software Engineering (ESEC/FSE) · doi:10.1145/3368089.3409705 · Cited by 24
“, 36, 41, 64, 86], lack of collaboration support [39], lack of management buy-in [e.”
BackgroundOn the adequacy of static analysis warnings with respect to code smell prediction
Pecorelli, F., Lujan, S., Lenarduzzi, V., Palomba, F., & Lucia, A. D. (2022) · Empirical Software Engineering · doi:10.1007/s10664-022-10126-5 · Cited by 25
Utture, A., Liu, S., Kalhauge, C. G., & Palsberg, J. (2022) · ACM/IEEE International Conference on Software Engineering: Companion Proceedings (ICSE-Companion) · doi:10.1145/3510003.3510166 · Cited by 19
“The high volume of warnings makes it cumbersome for developers to manually inspect and in practice this results in developers ignoring the tool output entirely [6, 25].”
BackgroundResultA variable-level automated defect identification model based on machine learning
Zhang, Y., Xing, Y., Gong, Y., Jin, D., Li, H., & Liu, F. (2019) · Soft Computing · doi:10.1007/s00500-019-03942-3 · Cited by 25
Leveraging Large Language Model for Automatic Patch Correctness Assessment
Zhou, X., Xu, B., Kim, K., Han, D., Nguyen, H. H., Le-Cong, T., He, J., Le, X.-B. D., & Lo, D. (2024) · IEEE Transactions on Software Engineering · doi:10.1109/tse.2024.3452252 · Cited by 45
Digital Nudges for Encouraging Developer Actions
Brown, C. (2019) · ACM/IEEE International Conference on Software Engineering: Companion Proceedings (ICSE-Companion) · doi:10.1109/icse-companion.2019.00082 · Cited by 19
“…practice of integrating tools into the development process, prior work has examined barriers preventing software engineers from adopting tools for debugging [6], static analysis [12], security [34], refactoring [21], documentation [9], open source contribution [18], and build automation [25].”
MethodUnderstanding the impact of GitHub suggested changes on recommendations between developers
Brown, C., & Parnin, C. (2020) · ACM Joint European Software Engineering Conference and Symposium on the Foundations of Software Engineering (ESEC/FSE) · doi:10.1145/3368089.3409722 · Cited by 22
“For instance, Johnson and colleagues propose using concise messages in a quick fix design to automatically provide fixes to reported bugs and encourage developers to adopt code-checking systems [30].”
BackgroundTrust in Collaborative Automation in High Stakes Software Engineering Work: A Case Study at NASA
Widder, D. G., Dabbish, L., Herbsleb, J. D., Holloway, A., & Davidoff, S. (2021) · Proceedings of the 2021 CHI Conference on Human Factors in Computing Systems · doi:10.1145/3411764.3445650 · Cited by 17
“Programming is increasingly conducted using tools which automate previously manual actions: such automated tools can help software engineers code [6], write tests [11], build [16], find bugs [26], repair [31], and deploy [33] their systems (also see Figure 1).”
MethodFormal model of IEC 61499 execution trace in FBME IDE
Liakh, T., Sorokin, R., Akifev, D., Patil, S., & Vyatkin, V. V. (2022) · IEEE International Conference on Industrial Informatics (INDIN) · doi:10.1109/indin51773.2022.9976176 · Cited by 18
“Some studies have shown that textural representation obstructs adaptation of formal verification methods to the software development cycle [12]; • Modules developers have to do routine operations to display execution trace on GUI.”
BackgroundLeveraging Practitioners’ Feedback to Improve a Security Linter
Reis, S., Abreu, R., d’Amorim, M., & Fortunato, D. (2022) · IEEE/ACM International Conference on Automated Software Engineering (ASE) · doi:10.1145/3551349.3560419 · Cited by 28
“Linters are often imprecise tools [4, 8, 12, 19, 22, 34].”
BackgroundResearch Trends, Detection Methods, Practices, and Challenges in Code Smell: SLR
Hilmi, M. A. A., Puspaningrum, A., Darsih, Siahaan, D., Samosir, H. S., & Rahma, A. S. (2023) · IEEE Access · doi:10.1109/access.2023.3334258 · Cited by 24
“For those who conduct studies related to real life, namely related to developers and software development, several studies are interesting to note, such as in studies [32], [33], [34], where it is sought to find out how developers respond or interact with code.”
BackgroundLet’s Fix this Together: Conversational Debugging with GitHub Copilot
Bajpai, Y., Chopra, B., Biyani, P., Aslan, C., Coleman, D., Gulwani, S., Parnin, C., Radhakrishna, A., & Soares, G. (2024) · IEEE Symposium on Visual Languages and Human-Centric Computing (VL/HCC) · doi:10.1109/vl/hcc60511.2024.00011 · Cited by 34
“Developers may have different levels of experience with debugging strategies [1], [5], [26] or debugging tools (e.g., breakpoints, watch expressions, etc.) [6]—less experienced developers may not even know of their existence or under-utilize them [7].”
BackgroundWhich Factors Influence Practitioners' Usage of Build Automation Tools?
Rahman, A., Partho, A., Meder, D., & Williams, L. A. (2017) · IEEE/ACM International Workshop on Rapid Continuous Software Engineering (RCoSE) · doi:10.1109/rcose.2017.8 · Cited by 28
“[13] investigated reasons about why developers do not want to use static analysis tools through systematic investigation of developer interviews.”
BackgroundCharacterizing Buffer Overflow Vulnerabilities in Large C/C++ Projects
Pereira, J. D., Ivaki, N., & Vieira, M. P. A. (2021) · IEEE Access · doi:10.1109/access.2021.3120349 · Cited by 17
“On one hand, although considered effective to point the problematic (or vulnerable) lines of code, SATs are known for reporting a high number of false alarms [13].”
BackgroundAutoLog: A Log Sequence Synthesis Framework for Anomaly Detection
Huo, Y., Li, Y., Su, Y., He, P., Xie, Z., & Lyu, M. R.-T. (2023) · IEEE/ACM International Conference on Automated Software Engineering (ASE) · doi:10.1109/ase56229.2023.00133 · Cited by 30
“The promising path finding time further manifests its scalability for real-world applications.”
BackgroundStatfier: Automated Testing of Static Analyzers via Semantic-Preserving Program Transformations
Zhang, H., Pei, Y., Chen, J., & Tan, S. H. (2023) · ACM Joint European Software Engineering Conference and Symposium on the Foundations of Software Engineering (ESEC/FSE) · doi:10.1145/3611643.3616272 · Cited by 43
“…tools because they (1) are widely used open-source tools for Java programs, (2) have been used in prior studies on static analyzers [3, 4, 18, 32, 42, 63], and (3) are representative of static analyzers adopted for different purposes (e.g., SonarQube supports automated code review, whereas…”
MethodA study of interactive code annotation for access control vulnerabilities
Thomas, T. W., Chu, B., Lipford, H. R., Smith, J., & Murphy-Hill, E. R. (2015) · IEEE Symposium on Visual Languages and Human-Centric Computing (VL/HCC) · doi:10.1109/vlhcc.2015.7357200 · Cited by 17
Self-citationInferring Bug Signatures to Detect Real Bugs
Zhong, H., Wang, X., & Mei, H. (2020) · IEEE Transactions on Software Engineering · doi:10.1109/tse.2020.2996975 · Cited by 23
First come first served: the impact of file position on code review
Fregnan, E., Braz, L., D’Ambros, M., Çalıklı, G., & Bacchelli, A. (2022) · ACM Joint European Software Engineering Conference and Symposium on the Foundations of Software Engineering (ESEC/FSE) · doi:10.1145/3540250.3549177 · Cited by 25
“To this aim, new solutions could be devised taking inspiration from previous studies on program-analysis tools [34, 39], where the authors investigated how warnings should be displayed to be welcomed by developers.”
BackgroundCode-line-level Bugginess Identification: How Far have We Come, and How Far have We Yet to Go?
Guo, Z., Liu, S., Liu, X., Lai, W., Ma, M., Zhang, X., Ni, C., Yang, Y., Li, Y., Chen, L., et al. (2023) · ACM Transactions on Software Engineering and Methodology · doi:10.1145/3582572 · Cited by 23
“, warnings) in the target software artifacts quickly without any dynamic execution process, it has been pointed out that most warnings are actually false positives [29, 34].”
BackgroundMethodI'd Like to Have an Argument, Please: Using Dialectic for Effective App Security
Weir, C., Rashid, A., & Noble, J. (2017) · European Symposium on Usable Security (EuroUSEC) · doi:10.14722/eurousec.2017.23002 · Cited by 16
The Usability (or Not) of Refactoring Tools
Eilertsen, A. M., & Murphy, G. C. (2021) · IEEE International Conference on Software Analysis, Evolution and Reengineering (SANER) · doi:10.1109/saner50967.2021.00030 · Cited by 16
Xypolytos, A., Xu, H., Vieira, B., & Eldin, A. A. (2017) · IEEE International Conference on Software Quality, Reliability and Security Companion (QRS-C) · doi:10.1109/qrs-c.2017.110 · Cited by 16
Detecting unknown inconsistencies in web applications
Ocariza, F. S., Pattabiraman, K., & Mesbah, A. (2017) · IEEE/ACM International Conference on Automated Software Engineering (ASE) · doi:10.1109/ase.2017.8115667 · Cited by 17
“tools [30], [31], we believe that they will not deter significantly the usability of HOLOCRON, based on our own analysis of the false positives that appeared in our experiment.”
BackgroundFoucault, M., Blanc, X., Falleri, J., & Storey, M. (2019) · Empirical Software Engineering · doi:10.1007/s10664-019-09719-4 · Cited by 20
Source Code Vulnerability Detection Based on Joint Graph and Multimodal Feature Fusion
Jin, D., He, C., Zou, Q., Qin, Y., & Wang, B. (2025) · Electronics · doi:10.3390/electronics14050975 · Cited by 19
Alami, A., & Ernst, N. (2025) · 2025 IEEE/ACM 18th International Conference on Cooperative and Human Aspects of Software Engineering (CHASE) · doi:10.1109/chase66643.2025.00016 · Cited by 15
“For example, Johnson et al. showed that reporting the factual outputs of the analysis is not sufficient for developers to adopt a static analysis tool [35].”
Automatic Static Vulnerability Detection for Machine Learning Libraries: Are We There Yet?
Harzevili, N. S., Shin, J., Wang, J., Wang, S., & Nagappan, N. (2023) · Proceedings/Proceedings - International Symposium on Software Reliability Engineering · doi:10.1109/issre59848.2023.00042 · Cited by 25
Explaining Static Analysis With Rule Graphs
Quang, L. N., & Bodden, E. (2020) · IEEE Transactions on Software Engineering · doi:10.1109/tse.2020.2999534 · Cited by 24
“Sometimes, this understanding may not match the developer’s, which results in uncertainties, a wrong treatment of critical warnings, wrong tool configurations, or even tool abandonment [8], [9].”
BackgroundInfluentialIoTBox: Sandbox Mining to Prevent Interaction Threats in IoT Systems
Kang, H. J., Sim, S. Q., & Lo, D. (2021) · IEEE International Conference on Software Testing, Verification and Validation (ICST) · doi:10.1109/icst49551.2021.00029 · Cited by 16
An Empirical Study Of Bad Smells During Software Evolution Using Designite Tool
(2018) · i-manager’s Journal on Software Engineering · doi:10.26634/jse.12.4.14958 · Cited by 20
Detecting Error-Handling Bugs without Error Specification Input
Jia, Z., Li, S., Yu, T., Liao, X., Wang, J., Liu, X., & Liu, Y. (2019) · IEEE/ACM International Conference on Automated Software Engineering (ASE) · doi:10.1109/ase.2019.00029 · Cited by 15
“[26] conducted interviews with 20 developers to ascertain why software developers do not use”
BackgroundMehrpour, S., & LaToza, T. D. (2022) · Empirical Software Engineering · doi:10.1007/s10664-022-10232-4 · Cited by 25
“Beyond simply identifying the presence of a defect, developers also increasingly expect Static Analysis Tools to help in the process of proposing a fix (Johnson et al. 2013).”
BackgroundAlOmar, E. A., AlOmar, S. A., & Mkaouer, M. W. (2023) · IEEE/ACM International Conference on Software Engineering: Software Engineering Education and Training (ICSE-SEET) · doi:10.1109/icse-seet58685.2023.00023 · Cited by 28
“little is known about their effectiveness in raising students’ awareness with respect to anti-patterns, given that these linters tend to generate a large number of false positives [2]–[5].”
BackgroundResultVulAdvisor: Natural Language Suggestion Generation for Software Vulnerability Repair
Zhang, J., Wang, C., Li, A., Wang, W., Li, T., & Liu, Y. (2024) · IEEE/ACM International Conference on Automated Software Engineering (ASE) · doi:10.1145/3691620.3695555 · Cited by 38
“It goes beyond mere accuracy of a model’s performance, but concerns the validity and reliability of its suggestion process, which is crucial for building a developer-centric tool [23, 56].”
Integrated static code analysis and runtime verification
Sözer, H. (2014) · Software Practice and Experience · doi:10.1002/spe.2287 · Cited by 14
“This process requires considerable time and effort such that the cost of using SCA tools overcomes its benefits [10].”
BackgroundBigSpa: An Efficient Interprocedural Static Analysis Engine in the Cloud
Zuo, Z., Gu, R., Jiang, X., Wang, Z., Huang, Y., Wang, L., & Li, X. (2019) · IEEE International Parallel and Distributed Processing Symposium (IPDPS) · doi:10.1109/ipdps.2019.00086 · Cited by 14
Using code reviews to automatically configure static analysis tools
Zampetti, F., Mudbhari, S., Arnaoudova, V., Penta, M. D., Panichella, S., & Antoniol, G. (2021) · Empirical Software Engineering · doi:10.1007/s10664-021-10076-4 · Cited by 20
“Obviously, for SCATs identifying likely defects, it might be useful to favor recall over precision, although previous research has warned about the limited adoption of SCATs due to low precision (Johnson et al. 2013; Wedyan et al. 2009).”
BackgroundMethodInfluential(2023) · doi:10.1109/ase56229.2023.00157 · Cited by 14
Khasawneh, M. A. S. (2023) · Studies in Media and Communication · doi:10.11114/smc.v12i1.6559 · Cited by 14
“Unfortunately, insufficient awareness on the part of both developers and end users often gets in the way of making full use of these features (Johnson et al., 2013).”
BackgroundDirected Dynamic Symbolic Execution for Static Analysis Warnings Confirmation
Gerasimov, A. Y. (2018) · Programming and Computer Software · doi:10.1134/s036176881805002x · Cited by 17
“In turn, low analysis precision, as well as the high complexity of the process of verification of the results of automated tools, lead to the fact that software developers refuse to use source code automated analysis tools [7, 8].”
BackgroundReducing False Positives of Static Analysis for SEI CERT C Coding Standard
Nguyen, T. T., Maleehuan, P., Aoki, T., Tomita, T., & Yamada, I. (2019) · doi:10.1109/cesser-ip.2019.00015 · Cited by 14
Concerns identified in code review: A fine-grained, faceted classification
Gunawardena, S. D., Tempero, E. D., & Blincoe, K. (2022) · Information and Software Technology · doi:10.1016/j.infsof.2022.107054 · Cited by 20
Graph-based visualization of merge requests for code review
Fregnan, E., Fröhlich, J., Spadini, D., & Bacchelli, A. (2022) · Journal of Systems and Software · doi:10.1016/j.jss.2022.111506 · Cited by 24
Towards Precise Reporting of Cryptographic Misuses
Chen, Y., Liu, Y., Wu, K. L., Le, D. V., & Chau, S. Y. (2024) · Network and Distributed System Security Symposium · doi:10.14722/ndss.2024.241032 · Cited by 20
“Back in 2013, [10] conducted a user study to investigate why developers are not widely adopting static analysis tools.”
BackgroundVulTR: Software vulnerability detection model based on multi-layer key feature enhancement
He, H., Wang, S., Wang, Y., Liu, K., & Yu, L. (2024) · Computers & Security · doi:10.1016/j.cose.2024.104139 · Cited by 14
Comparison of static analysis architecture recovery tools for microservice applications
Schneider, S., Bakhtin, A., Li, X., Soldani, J., Antonio Brogi, A., Cerny, T., Scandariato, R., & Taibi, D. (2025) · Empirical Software Engineering · doi:10.1007/s10664-025-10686-2 · Cited by 23
What You See is What You Get: Attention-Based Self-Guided Automatic Unit Test Generation
Yin, X., Ni, C., Xu, X., & Yang, X. (2025) · ACM/IEEE International Conference on Software Engineering: Companion Proceedings (ICSE-Companion) · doi:10.1109/icse55347.2025.00105 · Cited by 29
Revisiting context-based code smells prioritization
Sae‐Lim, N., Hayashi, S., & Saeki, M. (2017) · XP Scientific Workshops · doi:10.1145/3120459.3120463 · Cited by 13
“Consequently, developers do not use static analysis tools such as code smell detectors because of numerous detected warnings [10].”
BackgroundInvestigating the Current State of Security in Large-Scale Agile Development
Nägele, S., Watzelt, J.-P., & Matthes, F. (2022) · Lecture notes in business information processing · doi:10.1007/978-3-031-08169-9_13 · Cited by 22
Software Mining Studies: Goals, Approaches, Artifacts, and Replicability
Amann, S., Beyer, S., Kevic, K., & Gall, H. C. (2015) · Lecture notes in computer science · doi:10.1007/978-3-319-28406-4_5 · Cited by 14
“investigated on shortcomings of current bug-detection tools that keep developers from using them in practice [48].”
BackgroundAutomatically Generating Fix Suggestions in Response to Static Code Analysis Warnings
Marcílio, D., Furia, C. A., Bonifácio, R., & Pinto, G. (2019) · IEEE International Working Conference on Source Code Analysis and Manipulation (SCAM) · doi:10.1109/scam.2019.00013 · Cited by 13
“By working statically on the source or byte code of a project, these tools are applicable to large code bases [3], [4], where they quickly search for patterns that may indicate problems—bugs, questionable design choices, or failures to follow stylistic conventions [5], [6]—and report them to users.”
BackgroundSensei: Enforcing secure coding guidelines in the integrated development environment
Cremer, P. D., Desmet, N., Madou, M., & Sutter, B. D. (2020) · Software Practice and Experience · doi:10.1002/spe.2844 · Cited by 13
“11,18 They should instead quickly find out how to comply to the coding guideline without spending much time or effort.”
BackgroundFUM - A Framework for API Usage constraint and Misuse Classification
Schlichtig, M., Sassalla, S., Narasimhan, K., & Bodden, E. (2022) · IEEE International Conference on Software Analysis, Evolution and Reengineering (SANER) · doi:10.1109/saner53432.2022.00085 · Cited by 14
“, precision and recall), usability issues [12], and the Achilles heel of static analysis: false positives [30].”
BackgroundAn empirical assessment of machine learning approaches for triaging reports of static analysis tools
Yerramreddy, S., Mordahl, A., Koç, U., Wei, S., Foster, J. S., Carpuat, M. J., & Porter, A. (2023) · Empirical Software Engineering · doi:10.1007/s10664-022-10253-z · Cited by 17
“It is well known that false positives are a major barrier to the usage of analysis tools (Johnson et al. 2013), so we do not believe our scenario and the requirement of a balanced dataset are unrealistic.”
BackgroundA Case for Feminism in Programming Language Design
Hermans, F., & Schlesinger, A. (2024) · ACM SIGPLAN International Symposium on New Ideas, New Paradigms, and Reflections on Programming and Software (Onward!) · doi:10.1145/3689492.3689809 · Cited by 20
Ammonia: an approach for deriving project-specific bug patterns
Higo, Y., Hayashi, S., Hata, H., & Nagappan, M. (2020) · Empirical Software Engineering · doi:10.1007/s10664-020-09807-w · Cited by 12
“…current SA tool databases do not contain any specific bug patterns that are part of a particular target software project, and researchers like Johnson et al. have previously pointed out that this lack of customizability is one of the reasons why SA tools are infrequently used (Johnson et al. 2013).”
BackgroundMethodBrown, C., & Parnin, C. (2020) · doi:10.1145/3387940.3391506 · Cited by 17
“For instance, Johnson and colleagues discovered that the primary reasons developers reported for not using static analysis tools in their work is poor result understandability, customizability, and tool output [15].”
BackgroundGorski, P. L., Möller, S., Wiefling, S., & Iacono, L. L. (2021) · IEEE Transactions on Software Engineering · doi:10.1109/tse.2021.3094171 · Cited by 21
What happens in my code reviews? An investigation on automatically classifying review changes
Fregnan, E., Petrulio, F., Geronimo, L. D., & Bacchelli, A. (2022) · Empirical Software Engineering · doi:10.1007/s10664-021-10075-5 · Cited by 19
“(2014) and further supports the research aimed at improving static analysis tools to pinpoint potential issues in source code (Vassallo et al. 2018; Vassallo et al. 2019a; Di Penta et al. 2009; Johnson et al. 2013).”
BackgroundResult
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.