Identifying unmaintained projects in github

Coelho, Jailton; Valente, M.; Silva, Luciana L.; Shihab, Emad

doi:10.1145/3239235.3240501

Cited by 38 publications

(29 citation statements)

References 35 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…The recent work by Coelho et al [23] presented a machine learning based approach that uses standard metrics (number of commits, pull requests, contributors, etc.) extracted from Github to classify, whether maintenance of a particular project becomes dead.…”

Section: Maintenance Of Software Librariesmentioning

confidence: 99%

Vuln4Real: A Methodology for Counting Actually Vulnerable Dependencies

Pashchenko

Plate²,

Ponta³

et al. 2022

IIEEE Trans. Software Eng.

View full text Add to dashboard Cite

Vulnerable dependencies are a known problem in today's free open-source software ecosystems because FOSS libraries are highly interconnected, and developers do not always update their dependencies. Our paper proposes Vuln4Real, the methodology for counting actually vulnerable dependencies, that addresses the over-inflation problem of academic and industrial approaches for reporting vulnerable dependencies in FOSS software, and therefore, caters to the needs of industrial practice for correct allocation of development and audit resources. To understand the industrial impact of a more precise methodology, we considered the 500 most popular FOSS Java libraries used by SAP in its own software. Our analysis included 25767 distinct library instances in Maven. We found that the proposed methodology has visible impacts on both ecosystem view and the individual library developer view of the situation of software dependencies: Vuln4Real significantly reduces the number of false alerts for deployed code (dependencies wrongly flagged as vulnerable), provides meaningful insights on the exposure to third-parties (and hence vulnerabilities) of a library, and automatically predicts when dependency maintenance starts lagging, so it may not receive updates for arising issues.

show abstract

Section: Maintenance Of Software Librariesmentioning

confidence: 99%

Vuln4Real: A Methodology for Counting Actually Vulnerable Dependencies

Pashchenko

Plate²,

Ponta³

et al. 2022

IIEEE Trans. Software Eng.

View full text Add to dashboard Cite

show abstract

“…Another problem being solved by this researcher was identifying which of the seemingly abandoned projects may be "feature complete," i.e. already have the intended scope and do not require further maintenance [13]. Feature complete projects should be widely used in contrast to abandoned projects.…”

Section: Python Ecosystem Analysismentioning

confidence: 99%

“…Feature complete projects should be widely used in contrast to abandoned projects. Proxies of project usage, e.g., GitHub stars or forks can be used to identify such projects [13]. WoC, however, lets us measure the extent of use directly.…”

Section: Python Ecosystem Analysismentioning

confidence: 99%

World of Code: An Infrastructure for Mining the Universe of Open Source VCS Data

Bogart

Amreen

et al. 2019

2019 IEEE/ACM 16th International Conference on Mining Software Repositories (MSR)

View full text Add to dashboard Cite

Open source software (OSS) is essential for modern society and, while substantial research has been done on individual (typically central) projects, only a limited understanding of the periphery of the entire OSS ecosystem exists. For example, how are the tens of millions of projects in the periphery interconnected through technical dependencies, code sharing, or knowledge flow? To answer such questions we: a) create a very large and frequently updated collection of version control data in the entire FLOSS ecosystems named World of Code (WoC), that can completely cross-reference authors, projects, commits, blobs, dependencies, and history of the FLOSS ecosystems and b) provide capabilities to efficiently correct, augment, query, and analyze that data. Our current WoC implementation is capable of being updated on a monthly basis and contains over 18B Git objects. To evaluate its research potential and to create vignettes for its usage, we employ WoC in conducting several research tasks. In particular, we find that it is capable of supporting trend evaluation, ecosystem measurement, and the determination of package usage. We expect WoC to spur investigation into global properties of OSS development leading to increased resiliency of the entire OSS ecosystem. Our infrastructure facilitates the discovery of key technical dependencies, code flow, and social networks that provide the basis to determine the structure and evolution of the relationships that drive FLOSS activities and innovation.

show abstract

“…The reasons for the high acceptance of this issue includes a complete rework of the framework's API and the addition of long-standing feature requests. By contrast, the issue "Changing Redis master-slave replication terms with something else", 6 which was created by the repository owner, received the highest number of Thumbs down and Confused reactions. According to the comments in this issue, the proposal does not add value to the project and causes compatibility issues with previous versions.…”

Section: Rq #2: What Are the Most Common Reactions?mentioning

confidence: 99%

“…Borges et al [3] investigated the characteristics of popular GitHub repositories and found four major popularity growth patterns. Recently, Coelho et al [6] proposed an approach to identify unmaintained projects in GitHub. Their approach apply machine learning techniques and rely on metrics that measure the maintained level to identify and alert users.…”

Section: Related Workmentioning

confidence: 99%

Beyond Textual Issues

Borges¹,

Brito²,

Valente³

2019

Proceedings of the XXXIII Brazilian Symposium on Software Engineering

Self Cite

View full text Add to dashboard Cite

Recently, GitHub introduced a new social feature, named reactions, which are "pictorial characters" similar to emoji symbols widely used nowadays in text-based communications. Particularly, GitHub users can use a pre-defined set of such symbols to react to issues and pull requests. However, little is known about the real usage and impact of GitHub reactions. In this paper, we analyze the reactions provided by developers to more than 2.5 million issues and 9.7 million issue comments, in order to answer an extensive list of nine research questions about the usage and adoption of reactions. We show that reactions are being increasingly used by open source developers. Moreover, we also found that issues with reactions usually take more time to be handled and have longer discussions.

show abstract

Identifying unmaintained projects in github

Cited by 38 publications

References 35 publications

Vuln4Real: A Methodology for Counting Actually Vulnerable Dependencies

Vuln4Real: A Methodology for Counting Actually Vulnerable Dependencies

World of Code: An Infrastructure for Mining the Universe of Open Source VCS Data

Beyond Textual Issues

Contact Info

Product

Resources

About