# Analyzing Key Features of Open Source Software Survivability with Random Forest
## 1 Introduction  
Open source software (OSS) refers to software whose source code is freely available for use, modification, and distribution [1]. This openness fosters transparency and collaboration, allowing developers worldwide to contribute their ideas and expertise. As a result, OSS has become a significant driver of innovation, offering advantages such as cost efficiency, flexibility, and scalability [2, 3]. Platforms like GitHub play a pivotal role in managing OSS projects, providing tools for source code management, issue tracking, and contributor coordination. These platforms enable developers to work collaboratively across geographical boundaries, creating a dynamic and self-sustaining ecosystem that supports rapid software evolution. Despite these advantages, OSS projects face significant challenges due to their dependence on voluntary contributors. While some contributors are deeply involved in thelong-term maintenance of projects, many participate only sporadically or for short periods [4; 5]. This lack of consistent participation can lead to an accumulation of unresolved issues, such as bugs or feature requests, resulting in maintenance delays and reduced project reliability. These challenges are particularly problematic for OSS projects that lack dedicated maintenance personnel or established management frameworks. Over time, such delays hinder the project's ability to deliver updates or fix vulnerabilities, eroding user trust and diminishing software usability [6]. The impact of these challenges extends beyond individual projects, as OSS often serves as a foundation for commercial software systems and business applications. Unresolved vulnerabilities or maintenance failures in OSS can create cascading risks, affecting dependent systems and applications. For example, a poorly maintained OSS library used in a critical business system might lead to security breaches, system malfunctions, or even operational downtime [7]. Moreover, abandoned OSS projects, which no longer receive updates or security patches, leave developers with limited options. They must either seek alternative solutions or rebuild dependent software from scratch, which can be both costly and time-consuming [8; 9]. These issues underscore the critical need to evaluate and enhance OSS survivability to mitigate such risks. In this context, survivability refers to the ability of an OSS project to sustain itself and adapt over time by addressing maintenance challenges and continuing to improve [10]. High survivability indicates active community participation, efficient issue resolution, and the capability to deliver timely updates. Conversely, low survivability suggests inadequate maintenance, leading to unresolved bugs and eventual project abandonment. A key metric for assessing OSS survivability is the issue retention rate, which quantifies the probability of unresolved issues over time [11; 12]. Projects with high issue retention rates often face delayed problem-solving and reduced community engagement, whereas those with low rates exhibit efficient maintenance practices and strong community activity. This study focused on analyzing issue retention rates as a means of evaluating OSS survivability, identifying the factors influencing these rates, and offering insights to improve the long-term sustainability of OSS projects. This study evaluated the long-term survivability of open source software (OSS) projects by focusing on the issue retention rate as a critical metric. Survivability, in this context, refers to the ability of an OSS project to sustain itself through active maintenance, effective problem resolution, and consistent community participation. The issue retention rate, which quantifies the likelihood of unresolved issues over time, offers valuable insights into a project's maintenance capacity and overall health. Projects with high issue retention rates often face delayed problem-solving and reduced community engagement, which can significantly impact their ability to evolve and remain relevant.