Yutaro Kashiwa

Yutaro Kashiwa

Auto-generated profile, based on publicly available information

Yutaro Kashiwa

Nara Institute of Science and Technology, Japan

Research Focus & Metrics

Academic Career Length

6Years (2021-Present)

(Calculated once Scilit publication data is synced: current year − year of first publication + 1)

Representative Publications

View All Publications
6 March 2026 in ACM Transactions on Software Engineering and Methodology
Verified
Journal Article
Open access
MWMiku Watanabe
Miku Watanabe
HLHao Li
Hao Li
YKYutaro Kashiwa
Yutaro Kashiwa
BRBrittany Reid
Brittany Reid
HIHajimu Iida
Hajimu Iida
AHAhmed E. Hassan
Ahmed E. Hassan
Large language models (LLMs) are increasingly being integrated into software development processes. The ability to generate code and submit pull requests with minimal human intervention, through the use of autonomous AI agents, is poised to become a standard practice. However, little is known about the practical usefulness of these pull requests and the extent to which their contributions are accepted in real-world projects. In this paper, we empirically study 567 GitHub pull requests (PRs) generated using Claude Code, an agentic coding tool, across 157 diverse open-source projects. Our analysis reveals that developers tend to rely on agents for tasks such as refactoring, documentation, and testing. The results indicate that 83.8% of these agent-assisted PRs are eventually accepted and merged by project maintainers, with 54.9% of the merged PRs being integrated without further modification. The remaining 45.1% require additional changes and benefit from human revisions, especially for bug fixes, documentation, and adherence to project-specific standards. These findings suggest that while agent-assisted PRs are largely acceptable, they still benefit from human oversight and refinement.

5 February 2022 in Information and Software Technology
Verified
Journal Article
Closed access
YKYutaro Kashiwa
Yutaro Kashiwa
RNRyoma Nishikawa
Ryoma Nishikawa
YKYasutaka Kamei
Yasutaka Kamei
MKMasanari Kondo
Masanari Kondo
ESEmad Shihab
Emad Shihab
NUNaoyasu Ubayashi
Naoyasu Ubayashi

23 November 2023 in ACM Transactions on Software Engineering and Methodology
Verified
Journal Article
Open access
ONOlivier Nourry
Olivier Nourry
YKYutaro Kashiwa
Yutaro Kashiwa
BLBin Lin
Bin Lin
GBGabriele Bavota
Gabriele Bavota
MLMichele Lanza
Michele Lanza
YKYasutaka Kamei
Yasutaka Kamei
Fuzz testing, also known as fuzzing, is a software testing technique aimed at identifying software vulnerabilities. In recent decades, fuzzing has gained increasing popularity in the research community. However, existing studies led by fuzzing experts mainly focus on improving the coverage and performance of fuzzing techniques. That is, there is still a gap in empirical knowledge regarding fuzzing, especially about the challenges developers face when they adopt fuzzing. Understanding these challenges can provide valuable insights to both practitioners and researchers on how to further improve fuzzing processes and techniques. We conducted a study to understand the challenges encountered by developers during fuzzing. More specifically, we first manually analyzed 829 randomly sampled fuzzing-related GitHub issues and constructed a taxonomy consisting of 39 types of challenges (22 related to the fuzzing process itself, 17 related to using external fuzzing providers). We then surveyed 106 fuzzing practitioners to verify the validity of our taxonomy and collected feedback on how the fuzzing process can be improved. Our taxonomy, accompanied with representative examples and highlighted implications, can serve as a reference point on how to better adopt fuzzing techniques for practitioners, and indicates potential directions researchers can work on toward better fuzzing approaches and practices.

18 June 2024
Verified
Conference Paper
Open access
MWMiku Watanabe
Miku Watanabe
YKYutaro Kashiwa
Yutaro Kashiwa
BLBin Lin
Bin Lin
THToshiki Hirao
Toshiki Hirao
KYKen'IChi Yamaguchi
Ken'IChi Yamaguchi
HIHajimu Iida
Hajimu Iida
Code review is a critical but time-consuming process for ensuring code quality in modern software engineering. To alleviate the effort of reviewing source code, recent studies have investigated the possibility of automating the review process. Moreover, tools based on large language models such as ChatGPT are playing an increasingly important role in this vision. Understanding how these tools are used during code review can provide valuable insights for code review automation. This study investigates for what purposes developers use ChatGPT during code review and how developers react to the information and suggestions provided by ChatGPT. We manually analyze 229 review comments in 205 pull requests from 179 projects. We find that developers often use ChatGPT for outsourcing their work as frequently as asking for references. Moreover, we observe that only 30.7% of responses to the answers provided by ChatGPT are negative. We further analyze the reasons behind the negative reactions. Our results provide valuable insights for improving the effectiveness of LLMs in code reviews.

20 January 2025 in ACM Transactions on Software Engineering and Methodology
Verified
Journal Article
Open access
ONOlivier Nourry
Olivier Nourry
YKYutaro Kashiwa
Yutaro Kashiwa
WSWeiyi Shang
Weiyi Shang
HSHonglin Shu
Honglin Shu
YKYasutaka Kamei
Yasutaka Kamei
Fuzzing is an automated software testing technique used to find software vulnerabilities that works by sending large amounts of inputs to a software system to trigger bad behaviors. In recent years, the open source software ecosystem has seen a significant increase in the adoption of fuzzing to avoid spreading vulnerabilities throughout the ecosystem. While fuzzing can uncover vulnerabilities, there is currently a lack of knowledge regarding the challenges of conducting fuzzing activities over time. Specifically, fuzzers are very complex tools to set up and build before they can be used. We set out to empirically find out how challenging is build maintenance in the context of fuzzing. We mine over 1.2 million build logs from Google’s OSS-Fuzz service to investigate fuzzing build failures. We first conduct a quantitative analysis to quantify the prevalence of fuzzing build failures. We then manually investigate 677 failing fuzzing builds logs and establish a taxonomy of 25 root causes of build failures. We finally train a machine learning model to recognize common failure patterns in failing build logs. Our taxonomy can serve as a reference for practitioners conducting fuzzing build maintenance. Our modeling experiment shows the potential of using automation to simplify the process of fuzzing.

22 July 2022 in Empirical Software Engineering
Verified
Journal Article
Open access
PDF file
MKMasanari Kondo
Masanari Kondo
YKYutaro Kashiwa
Yutaro Kashiwa
YKYasutaka Kamei
Yasutaka Kamei
OMOsamu Mizuno
Osamu Mizuno
The accuracy of the SZZ algorithm is pivotal for just-in-time defect prediction because most prior studies have used the SZZ algorithm to detect defect-inducing commits to construct and evaluate their defect prediction models. The SZZ algorithm has two phases to detect defect-inducing commits: (1) linking issue reports in an issue-tracking system to possible defect-fixing commits in a version control system by using an issue-link algorithm (ILA); and (2) tracing the modifications of defect-fixing commits back to possible defect-inducing commits. Researchers and practitioners can address the second phase by using existing solutions such as a tool called . In contrast, although various ILAs have been proposed for the first phase, no large-scale studies exist in which such ILAs are evaluated under the same experimental conditions. Hence, we still have no conclusions regarding the best-performing ILA for the first phase. In this paper, we compare 10 ILAs collected from our systematic literature study with regards to the accuracy of detecting defect-fixing commits. In addition, we compare the defect prediction performance of ILAs and their combinations that can detect defect-fixing commits accurately. We conducted experiments on five open-source software projects. We found that all ILAs and their combinations prevented the defect prediction model from being affected by missing defect-fixing commits. In particular, the combination of a natural language text similarity approach, Phantom heuristics, a random forest approach, and a support vector machine approach is the best way to statistically significantly reduced the absolute differences from the ground-truth defect prediction performance. We summarized the guidelines to use ILAs as our recommendations.