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 401–500 of 567
A DSL for Resource Checking Using Finite State Automaton-Driven Symbolic Execution
Fülöp, E., & Pataki, N. (2020) · Open Computer Science · doi:10.1515/comp-2020-0120 · Cited by 2
“While most static analysis methods are designed to detect anomalies (called bugs) in software code, themethods they employ are varied [1].”
BackgroundErnst Denert Award for Software Engineering 2019: Practice Meets Foundations
Felderer, M., Hasselbring, W., Koziolek, H., Matthes, F., Prechelt, L., Reussner, R., Rumpe⋆, B., & Schaefer, I. (2020) · Springer eBooks · doi:10.1007/978-3-030-58617-1 · Cited by 4
SecurityGuard: An Automated Secure Coding Framework
Javed, Y., Arian, Q. A., & Alenezi, M. (2021) · Communications in computer and information science · doi:10.1007/978-3-030-71711-7_25 · Cited by 2
Open Data-driven Usability Improvements of Static Code Analysis and its Challenges
Söderberg, E., Church, L., & Höst, M. (2021) · International Conference on Evaluation and Assessment in Software Engineering (EASE) · doi:10.1145/3463274.3463808 · Cited by 2
“[13] later further highlighted these issues in a study where they investigate why developers are not using static analysis tools to find bugs.”
BackgroundReview of Static Analyzer Service Models
Menshikov, M. (2021) · Proceedings of the Institute for System Programming of RAS · doi:10.15514/ispras-2021-33(3)-2 · Cited by 2
“Working out a way to support all models contributes to developing a more unified analyzer structure, improving user experience [4], and, ultimately, may lead to wider adoption of static analysis tools.”
Backgroundإستعراض منهجی للأدبیات حول الکشف عن نقاط ضعف البرمجیات بإستخدام أسالیب تعلم الألة
رمضان, أ. ا. ک. ا., بهاء, أ., & غنیم, ع. (2022) · النشرة المعلوماتية في الحاسبات والمعلومات · doi:10.21608/fcihib.2022.87660.1058 · Cited by 2
Dancing, not Wrestling: Moving from Compliance to Concordance for Secure Software Development
Ashenden, D., Ollis, G., & Reid, I. (2022) · IEEE/ACM International Conference on Automated Software Engineering (ASE) · doi:10.1145/3551349.3561145 · Cited by 2
“This enables us to build on the few research studies that take a practice perspective of secure software development [14][11][24].”
BackgroundAre Neural Bug Detectors Comparable to Software Developers on Variable Misuse Bugs?
Richter, C., Haltermann, J., Jakobs, M.-C., Pauck, F., Schott, S., & Wehrheim, H. (2022) · IEEE/ACM International Conference on Automated Software Engineering (ASE) · doi:10.1145/3551349.3561156 · Cited by 6
“Bug detection done via static analysis often suffers from a high number of false alarms and this has been observed to be a major obstacle to the usage of such tools [19, 37, 46].”
BackgroundA Hierarchical Topical Modeling Approach for Recommending Repair of Quality Bugs
Krasniqi, R., & Do, H. (2023) · IEEE International Conference on Software Analysis, Evolution and Reengineering (SANER) · doi:10.1109/saner56733.2023.00014 · Cited by 3
“However, such approaches do not explain why source code might be faulty [24], nor they help software developers find the path leading to buggy behavior [46].”
BackgroundIdentification and analysis of change ripples in object-oriented software applications
Singh, R. K., & Agrawal, A. (2023) · Sadhana · doi:10.1007/s12046-023-02137-9 · Cited by 2
“Although many tools for identifying dependent entities in software applications are available in the literature [5–8], research shows that developers avoid using these tools and rely more on intuition or experience for code changes [9, 10].”
MethodUncovering Hidden Dependencies: Constructing Intelligible Path Witnesses using Dataflow Analyses
Umann, K., Horváth, G., & Porkoláb, Z. (2024) · Acta Cybernetica · doi:10.14232/actacyb.299805 · Cited by 2
Reducing accidental clones using instant clone search in automatic code review
Balachandran, V. (2020) · IEEE International Conference on Software Maintenance (ICSM) · doi:10.1109/icsme46990.2020.00089 · Cited by 2
Conversational Code Analysis: The Future of Secure Coding
Nembhard, F., & Carvalho, M. (2022) · IntechOpen eBooks · doi:10.5772/intechopen.98362 · Cited by 3
Shen, M., Pillai, A. A., Yuan, B. A., Davis, J. C., & Machiry, A. (2023) · arXiv · doi:10.48550/arxiv.2310.00205 · Cited by 1
“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.”
InfluentialEffects of Precise and Imprecise Value-Set Analysis (VSA) Information on Manual Code Analysis
Matzen, L. E., Leger, M., & Reedy, G. (2021) · Workshop on Binary Analysis Research (BAR) · doi:10.14722/bar.2021.23002 · Cited by 2
“The goals of these studies include comparing specific tools [49], understanding why available tools are not used [23], [40], evaluating the utility of a single tool [2], [28], and discovering information requirements of would-be users [41].”
BackgroundStudying the impact of risk assessment analytics on risk awareness and code review performance
Yu, X., Cogo, F. R., McIntosh, S., & Godfrey, M. W. (2024) · Empirical Software Engineering · doi:10.1007/s10664-024-10443-x · Cited by 3
Iftikhar, U., Börstler, J., bin Ali, N., & Kopp, O. (2025) · Software Quality Journal · doi:10.1007/s11219-025-09720-9 · Cited by 3
Sound Static Data Race Verification for C: Is the Race Lost?
Holter, K., Saan, S., Lam, P., & Vojdani, V. (2025) · ACM Transactions on Programming Languages and Systems · doi:10.1145/3732933 · Cited by 1
“However, we started from the SV-COMP competition suite as well as the Concrat real-world suite; both of these suites were curated by others.”
A Multi-Dimensional Visual Analytics Tool for the Security Posture of Open-Source Software
Li, T., Lu, C., & Lagaisse, B. (2025) · doi:10.1109/svm66695.2025.00007 · Cited by 1
“However, these tools have limitations, including high false-positive rates and text-based reports that are time-intensive to interpret [2].”
Hou, Z., Duan, Z., Yang, M., Wu, M., & Yang, S. (2025) · IEEE International Conference on Software Quality, Reliability and Security (QRS) · doi:10.1109/qrs65678.2025.00015 · Cited by 1
“A representative work is [5] [31].”
AI Mentor System: Building a Technical Debt Dashboard for Low Code
Lemos, A., & Coutinho, J. (2025) · IEEE International Conference on Software Maintenance (ICSM) · doi:10.1109/icsme64153.2025.00068 · Cited by 3
What Challenges Do Developers Face When Using Verification-Aware Programming Languages?
de Oliveira, F. K., Mendes, A., & Carreira, C. (2025) · Proceedings/Proceedings - International Symposium on Software Reliability Engineering · doi:10.1109/issre66568.2025.00031 · Cited by 9
Gamifying User Feedback Collection on Static Program Analysis Tools
Dahlbo, E., Lundmark, E., Söderberg, E., Eneroth, L., Höst, M., & Borg, M. (2025) · doi:10.1109/gamify66603.2025.00007 · Cited by 1
“Second, the large number of false positive warnings is a well-known challenge [9].”
InfluentialWüppelmann, D., & Yigitbas, E. (2025) · International Conference on Evaluation and Assessment in Software Engineering (EASE) · doi:10.1145/3756681.3756939 · Cited by 1
“Currently, if there are collaboration features, they provide asynchronous communication through comments or similar review functionalities [14].”
Explaining Code Risk in OSS: Towards LLM-Generated Fault Prediction Interpretations
Adejumo, E. K., & Johnson, B. (2025) · IEEE/ACM International Conference on Automated Software Engineering Workshops (ASEW) · doi:10.1109/asew67777.2025.00046 · Cited by 4
“Furthermore, lack of explanation behind tool notifications has been known to increase cognitive load, hinder trust, and reduce the likelihood of adoption and use [9], [10].”
Self-citationMutation-based Evaluation of Cryptographic API Misuse Detectors
Ami, A. S., Marsden, S., Moran, K., Poshyvanyk, D., & Nadkarni, A. (2026) · ACM Transactions on Privacy and Security · doi:10.1145/3796221 · Cited by 6
Determining the Unreachable: Constraint-Guided Reachability Analysis for Dependency Vulnerabilities
Feng, W., Li, X., Feng, R., Zhang, Y., Li, Y., Zhou, Z., Wang, Y., & Li, Y. (2026) · Proceedings of the ACM on Programming Languages · doi:10.1145/3798255 · Cited by 1
“Without incorporating reachability analysis, security tools may produce excessive false positives and low-priority alerts, overloading teams and wasting resources [Jacobs et al. 2021; Johnson et al. 2013].”
On Effort Awareness for Just-In-Time Defect Prediction
Bludau, P., & Pretschner, A. (2026) · Lecture notes in business information processing · doi:10.1007/978-3-032-24216-7_2 · Cited by 1
Saleem, A., Adnan, Z., Ryan, S. A., Jamıl, A., Hameed, A. A., & Fargetta, G. (2026) · IEEE International Conference on Secure IoT, Assured and Trusted Computing (SATC) · doi:10.1109/satc69565.2026.11542535 · Cited by 1
“Tools built on abstract syntax tree (AST) parsing detect common defects and style violations by matching known patterns [3].”
Security issues in python open-source software: a mining study from GitHub
Nocera, S., Romano, S., Francese, R., & Scanniello, G. (2026) · Empirical Software Engineering · doi:10.1007/s10664-026-10890-8 · Cited by 2
Decompiling the Web: Automated Semantic Recovery of Post-compilation Abstraction Leaks
Anonymous, & Liu, Y. (2026) · IEEE/ACM International Conference on Automated Software Engineering (ASE) · doi:10.1145/3832783.3837419 · Cited by 1
Emerging Trends and Challenges Toward LLM Agents in Static Analysis
Hua, H.-Q.-B., & Le, X.-B. (2026) · Lecture notes in computer science · doi:10.1007/978-981-92-2885-0_9 · Cited by 1
Le, T.-H.-C., Hua, H.-Q.-B., & Le, X.-B. (2026) · IEEE/ACM International Conference on Automated Software Engineering (ASE) · doi:10.1145/3832783.3834420 · Cited by 1
Preliminary findings on FOSS dependencies and security
Николаевич, П. И., Vu, D., & Massacci, F. (2020) · ACM/IEEE International Conference on Software Engineering: Companion Proceedings (ICSE-Companion) · doi:10.1145/3377812.3390903 · Cited by 1
“, [6, 11]) provide interesting insights into the software developers’ experience, but do not consider dependency analysis tools, and therefore, do not study how developers can use them to discover and mitigate security issues introduced by software dependencies.”
BackgroundSupporting Proactive Refactoring: An Exploratory Study on Decaying Modules and Their Prediction
Sae‐Lim, N., Hayashi, S., & Saeki, M. (2021) · IEICE Transactions on Information and Systems · doi:10.1587/transinf.2020edp7255 · Cited by 1
“This phenomenon may be comparable to the fact that static analysis tools are not used well by developers owing to a large number of detected warnings [28].”
BackgroundAre the Scala Checks Effective? Evaluating Checks with Real-world Projects
Zhang, X., Yan, J., Cui, B., Yan, J. H., & Zhang, J. (2021) · IEEE International Conference on Software Quality, Reliability and Security (QRS) · doi:10.1109/qrs54544.2021.00107 · Cited by 1
jGuard: Programming Misuse-Resilient APIs
Binder, S., Narasimhan, K., Kernig, S., & Mezini, M. (2022) · ACM SIGPLAN International Conference on Software Language Engineering (SLE) · doi:10.1145/3567512.3567526 · Cited by 1
“A problem with both allow-listing and deny-listing approaches is that application programmers may be reluctant to add additional tooling into their workflows [16] (P2).”
BackgroundContext-Sensitive Meta-Constraint Systems for Explainable Program Analysis
Apinis, K., & Vojdani, V. (2023) · Lecture notes in computer science · doi:10.1007/978-3-031-30820-8_27 · Cited by 1
A Static Analysis Platform for Investigating Security Trends in Repositories
Sonnekalb, T., Knaust, C.-T., Gruner, B., Brust, C.-A., Heinze, T. S., von Kurnatowski, L., Schreiber, A., & Mäder, P. (2023) · doi:10.1109/svm59160.2023.00005 · Cited by 1
“[2] found in interviews that developers find using these tools too burdensome and do not consider using bug tracking tools due to time constraints.”
BackgroundSecure CodeCity: 3-dimensional visualization of software security facets
Wijesiriwardana, C., Wimalaratne, P., Abeysinghe, T., Shalika, S., Ahmed, N., & Mufarrij, M. (2023) · Journal of the National Science Foundation of Sri Lanka · doi:10.4038/jnsfsr.v51i3.11201 · Cited by 1
A study of behavioral decay in design patterns
Reimanis, D., & Izurieta, C. I. (2023) · Journal of Software Evolution and Process · doi:10.1002/smr.2638 · Cited by 1
Realizing Refactoring Prediction through Deep Learning
Pereira, L. R. R., Pereira, D. L., & Durelli, R. S. (2023) · doi:10.5753/ise.2023.235749 · Cited by 3
“Consequently, the strategy of relying solely on static and heuristic analysis tools may not be as effective [16].”
MethodCapturing Contextual Relationships of Buggy Classes for Detecting Quality-Related Bugs
Krasniqi, R., & Do, H. (2023) · IEEE International Conference on Software Maintenance (ICSM) · doi:10.1109/icsme58846.2023.00048 · Cited by 1
“While spectrum-based fault localization techniques [1], [34] have effectively localized bugs [4], they fail to guide developers towards the paths leading to the buggy behavior [13].”
BackgroundFormal Runtime Error Detection During Development in the Automotive Industry
Hecking-Harbusch, J., Quante, J., & Schlund, M. (2023) · Lecture notes in computer science · doi:10.1007/978-3-031-50524-9_1 · Cited by 1
Fault Localization of Software: A Literature Review
Wang, Z., & Zeng, F. (2023) · IEEE International Conference on Software Quality, Reliability and Security Companion (QRS-C) · doi:10.1109/qrs-c60940.2023.00119 · Cited by 1
“…Johnson and others (2013) titled "Why don't software developers use static analysis tools to fmd bugs?" interviewed 20 developers and found that despite all participants acknowledging the benefits, obstacles to usage included issues like false positives and the presentation of warnings [7].”
BackgroundUnleashing the Power of Clippy in Real-World Rust Projects
Li, C., Yu, Y., Wu, H., Carlig, L., Nie, S., & Jiang, L. (2024) · ACM/IEEE International Conference on Software Engineering: Companion Proceedings (ICSE-Companion) · doi:10.1145/3639478.3643096 · Cited by 1
“Numerous user studies [30, 33, 34, 42, 45, 46] have been conducted to explore users’ experiences with linters.”
BackgroundInfluentialZhou, Y., Liu, X., Guo, Z., Zhou, Y., Zhang, C., & Qian, J. (2024) · Journal of Software Evolution and Process · doi:10.1002/smr.2696 · Cited by 2
Enhancing Field Tracking and Interprocedural Analysis to Find More Null Pointer Exceptions
Xie, D., Chen, B., Huang, K., Wang, Y., Pan, L., Chen, Z., & Peng, X. (2024) · IEEE International Conference on Software Analysis, Evolution and Reengineering (SANER) · doi:10.1109/saner60148.2024.00093 · Cited by 1
Enhancing Software Design and Developer Experience Via LLMs
Sun, S. (2024) · IEEE/ACM International Conference on Automated Software Engineering (ASE) · doi:10.1145/3691620.3695606 · Cited by 1
“Additionally, by studying CI jobs, we find it can be time-consuming, and developers often seek expedited results from these pipelines [7].”
Unveiling Heisenbugs with Diversified Execution
Ramesh, A., Huang, T., Riar, J., Titzer, B. L., & Rowe, A. (2025) · Proceedings of the ACM on Programming Languages · doi:10.1145/3720428 · Cited by 1
Singh, A. K., Tomar, D., Ammasai, V., & Manogaran, U. (2025) · AIP conference proceedings · doi:10.1063/5.0262307 · Cited by 1
The software testing community and IT stereotypes: a study with industry professionals
Evans, I., Porter, C., & Micallef, M. J. (2025) · Interacting with Computers · doi:10.1093/iwc/iwaf047 · Cited by 1
Adapting program analysis tool notifications to the individual developer
Johnson, B. (2015) · IEEE Symposium on Visual Languages and Human-Centric Computing (VL/HCC) · doi:10.1109/vlhcc.2015.7357232 · Cited by 2
“However, research suggests that developers are not always able to parse and understand the output provided by tools like FindBugs [8].”
BackgroundSelf-citationSharing and Preserving Coding Best Practices through Programmer Data Analytics
Bashani, S., & Perera, I. (2018) · International Conference on Advances in ICT for Emerging Regions · doi:10.1109/icter.2018.8615547 · Cited by 1
Investigation of Coding Violations Focusing on Authorships of Source Files
Burhandenny, A. E., Aman, H., & Kawahara, M. (2017) · International Conference on Applied Computing and Information Technology / International Conference on Computational Science and Intelligence (ACIT-CSI) · doi:10.1109/acit-csii-bcd.2017.44 · Cited by 1
Ammonia: An Approach for Deriving Project Specific Bug Patterns
Higo, Y., Hayashi, S., Hata, H., & Nagappan, M. (2020) · Institutional Repositories DataBase (IRDB) · Cited by 1
Declarative Demand-Driven Reverse Engineering
Sun, Y., Ching, J., & Micinski, K. (2021) · Workshop on Binary Analysis Research (BAR) · doi:10.14722/bar.2021.23016 · Cited by 1
IEEE Computer Graphics & Applications
(2021) · IEEE Software · doi:10.1109/ms.2021.3082586 · Cited by 1
Pistoia, M., Tripp, O., & Lubensky, D. M. (2017) · IGI Global eBooks · doi:10.4018/978-1-5225-3422-8.ch047 · Cited by 1
What really is software design?
Viviani, G., & Murphy, G. C. (2022) · IEEE International Conference on Software Analysis, Evolution and Reengineering (SANER) · doi:10.1109/saner53432.2022.00046 · Cited by 1
Teaming Humans with Virtual Assistants to Detect and Mitigate Vulnerabilities
Nembhard, F., & Carvalho, M. (2023) · Lecture notes in networks and systems · doi:10.1007/978-3-031-37717-4_35 · Cited by 3
A Method for Comparing and Selecting Static Code Analysis Tools in Software Development ProjectsPreprint
Haertel, C., Pohl, M., Staegemann, D. G., & Turowski, K. (2022) · Research Square · doi:10.21203/rs.3.rs-1546855/v1 · Cited by 1
Towards Applicable Just-In-Time Defect Prediction: A Practical Perspective on Effort AwarenessPreprint
Bludau, P., & Pretschner, A. (2024) · Research Square · doi:10.21203/rs.3.rs-4716570/v1 · Cited by 1
Explainable Vulnerability Detection in C/C++ Using Edge-Aware Graph Attention NetworksPreprint
Haque, R., Ali, A. H., McClean, S. I., & Khan, N. A. (2025) · SSRN Electronic Journal · doi:10.2139/ssrn.5404611 · Cited by 1
Enhancing tools' intelligence for improved program analysis tool usability
Johnson, B. (2014) · IEEE Symposium on Visual Languages and Human-Centric Computing (VL/HCC) · doi:10.1109/vlhcc.2014.6883050
Self-citationPrácticas de Desarrollo Software: Un Estudio Exploratorio con Herramientas de Análisis Estático
Tumino, M. C., & Bournissen, J. M. (2015) · Revista Latinoamericana de Ingenieria de Software · doi:10.18294/relais.2015.155-160
“[13] Johnson, Brittany, Song, Yoonki, Murphy-Hill, Emerson y Bowdidge.”
BackgroundInfluentialOn Mitigation of Modern Cybercrime Threats
Jovanović, M., Rančić, N., Davidović, D., & Mitić, D. (2016) · International Scientific Conference Sinteza · doi:10.15308/sinteza-2016-137-142
“However, these kinds of tools are alleged not to be used by developers as often as they ought to (Johnson et al., 2013).”
BackgroundResolving input validation vulnerabilities by retracing taint flow through source code
Smith, J. (2016) · IEEE Symposium on Visual Languages and Human-Centric Computing (VL/HCC) · doi:10.1109/vlhcc.2016.7739702
“Unfortunately, analysis tools do not effectively support developers in resolving the defects they detect [4].”
BackgroundA study on low complexity models to predict flaws in the Linux source code
Kanashiro, L., Ribeiro, A., Silva, D., Meirelles, P., & Terceiro, A. S. D. A. (2017) · Iberian Conference on Information Systems and Technologies (CISTI) · doi:10.23919/cisti.2017.7975747
“It is also known that static analysis helps programmers detect software vulnerabilities before they reach production [8] in a cheaper way than solely conducting manual inspections [9], thus the interest in static analyzers.”
BackgroundAre Your Classes Well-Encapsulated? Encapsulation Analysis for Java
Tang, Z., Zhai, J., Li, B., & Zhao, J. (2017) · IEEE International Conference on Software Quality, Reliability and Security (QRS) · doi:10.1109/qrs.2017.31
An Evaluation of Coding Violation Focusing on Change History and Authorship of Source File
Burhandenny, A. E., Aman, H., & Kawahara, M. (2017) · The International journal of networked and distributed computing · doi:10.2991/ijndc.2017.5.4.3
Generative Modeling Games for Exploratory Industry-Academic Research
Walenstein, A., & Malton, A. J. (2019) · doi:10.1109/cesser-ip.2019.00011
Applications of Synchronized Pushdown Systems
Späth, J. (2020) · Springer eBooks · doi:10.1007/978-3-030-58617-1_3
“In all cases, neither developers nor security experts are willing to use data-flow techniques on a daily basis [15].”
BackgroundVulnerability detection on web browsers
Yu, H. (2019) · doi:10.32657/10356/143063
Ernst Denert Award for Software Engineering 2022: Practice Meets Foundations
Bodden, E., Felderer, M., Hasselbring, W., Herber, P., Koziolek, H., Lilienthal, C., Matthes, F., Prechelt, L., Rumpe⋆, B., & Schaefer, I. (2024) · Springer eBooks · doi:10.1007/978-3-031-44412-8
What are the critical security flaws in my system?
Fördős, V. (2021) · ACM SIGPLAN Workshop on Erlang (Erlang) · doi:10.1145/3471871.3472965 · Cited by 1
“The authors of [17] investigated why developers are not using security checkers and they found that the existence of false positives is one of the obstacles.”
BackgroundNovice understanding of program analysis tool notifications
Johnson, B. (2013) · ACM/IEEE International Conference on Software Engineering: Companion Proceedings (ICSE-Companion) · doi:10.1109/icse.2013.6606735
“Index Terms—program analysis; notifications; tool evaluation”
Self-citationMethod Using Command Abstraction Library for Iterative Testing Security of Web Applications
Munetoh, S., & Yoshioka, N. (2017) · IGI Global eBooks · doi:10.4018/978-1-5225-3422-8.ch008
CHANGEVIZ: Enhancing the GitHub Pull Request Interface with Method Call Information
Gasparini, L., Fregnan, E., Braz, L., Baum, T., & Bacchelli, A. (2021) · doi:10.26226/morressier.613b545d842293c031b5b9a0
A Tool for Syntactic Dependency Analysis on the Web Stack
Kalsi, M. S., Gary, K. A., Gupta, V., & Das, S. (2022) · Advances in intelligent systems and computing · doi:10.1007/978-3-030-97652-1_4
Building A Moat: Fortifying Satellite Software from Vulnerabilities
Rose, G. J., Henry, W. C., Hodson, D. D., & Falco, G. J. (2022) · AIAA Accelerating Space Commerce, Exploration, and New Discovery Conference (ASCEND) · doi:10.2514/6.2022-4329
Assessment of Automated (Intelligent) Toolchains
Papotti, A. (2022) · IEEE/ACM International Conference on Automated Software Engineering (ASE) · doi:10.1145/3551349.3559572
“For example, in the automated detection of security vulnerabilities, static and dynamic analysis based tools suffer from high false-positive/false-negative rates [7, 11].”
BackgroundAn Evaluation of General-Purpose Static Analysis Tools on C/C++ Test Code
Malm, J., Enoiu, E. P., Masud, A. N., Lisper, B., Porkoláb, Z., & Eldh, S. (2022) · Euromicro Conference on Software Engineering and Advanced Applications (SEAA) · doi:10.1109/seaa56994.2022.00029
“3Representatives from telecommunication and automotive domains of issues is supported through suggestions of code changes, which we remind the reader is a request from practitioners for for adoption in practice [9].”
BackgroundWindArms: More Efficient DGF Coverage-Guided Tracing
Luo, Y., Peng, J., & Lin, J. (2022) · IEEE International Conference on Communication Technology (ICCT) · doi:10.1109/icct56141.2022.10073335
“Compared with Coverage-guided GrayBox Fuzzing(CGF), DGF is mainly used in patch testing [4][5], crash reproduction [6][7], static analysis report verification [8][9], etc.”
MethodMulti-granularity Deep Vulnerability Detection Using Graph Neural Networks
Yang, T., Lian, S., Jia, Q., Hu, C., & Guo, S. (2023) · Communications in computer and information science · doi:10.1007/978-981-99-8184-7_12
Usefulness of Automatic Static Analysis Tools: Evidence from Four Case Studies
Trautsch, A. (2024) · Springer eBooks · doi:10.1007/978-3-031-44412-8_6
Customized Security Triage from Analysis Tools: Current State of the Art
Wu, Y. X., Su, J., Moran, D. D., & Near, C. D. (2023) · IEEE International Conference on Computer and Communications (ICCC) · doi:10.1109/iccc59590.2023.10507350 · Cited by 1
“The researchers Johnson et al [11] investigated possible reasons why SATs are not broadly used by software developers and proposed other expectations for these tools.”
BackgroundKrasniqi, R. (2024) · University of North Texas Digital Library (University of North Texas) · doi:10.12794/metadc2332577
Supporting Error Chains in Static Analysis for Precise Evaluation Results and Enhanced Usability
Wickert, A.-K., Schlichtig, M., Vogel, M., Winter, L., Mezini, M., & Bodden, E. (2024) · IEEE International Conference on Software Analysis, Evolution and Reengineering (SANER) · doi:10.1109/saner60148.2024.00076 · Cited by 2
“However, no previous work inspected the dependencies between cryptographic misuses. c) Usability of Security Warnings: Previous work has shown that a high false positive rate hinders the adaption of a static analysis [10], [11], [13].”
BackgroundInfluentialIntroducing a Linter in an Industrial Lua Code Base
Walchshofer, A., Fischer, S., Wöß, A., Duque‐Torres, A., Löberbauer, M., & Koll, G. (2024) · IEEE International Conference on Software Analysis, Evolution and Reengineering - Companion (SANER-C) · doi:10.1109/saner-c62648.2024.00032
UNG: A Diagnostic Standard C Library
Kaivo, J. K. (2024) · doi:10.33915/etd.12537
Co-Designing Web Interfaces for Code Comparison
Middleton, J., Patil, N., & Stolee, K. T. (2024) · IEEE Symposium on Visual Languages and Human-Centric Computing (VL/HCC) · doi:10.1109/vl/hcc60511.2024.00029 · Cited by 2
“For example, Johnson and colleagues use elements of a PD approach to learn how developers prefer static analysis tools [43], and Gorski and colleagues apply it within focus groups to sketch better warnings for cryptographic APIs [44].”
BackgroundUnderstanding Developer-Analyzer Interactions in Code Reviews
Schäf, M., Çirişci, B., Luo, L., Mansur, M. N., Tripp, O., Sanchez, D., Zhou, Q., & Zafar, M. B. (2024) · IEEE/ACM International Conference on Automated Software Engineering (ASE) · doi:10.1145/3691620.3695257 · Cited by 1
“Several studies have found that including static code analyzers in the code review process is an effective way to detect and eliminate software bugs early in the software development process (e.g., [1–7]).”
Mahmood, M. B., Wu, G., Iqbal, T., Ejaz, M. A., & Khan, L. (2024) · SSRN Electronic Journal · doi:10.2139/ssrn.5041670
Adding Context to Automated Vulnerability Detection for Teaching Software Security
Dorard, A., Küppers, B., Sai, A. R., & Schnitzler, T. (2025) · ACM Conference on Innovation and Technology in Computer Science Education (ITiCSE) · doi:10.1145/3724389.3730794
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.