A Systematic Mapping Study of Software Development With GitHub
Open accessThe DOI matches its Crossref record; 4 of the 4 references it cites were found in a registry or an index.
Abstract
Context: GitHub, nowadays the most popular social coding platform, has become the reference for mining Open Source repositories, a growing research trend aiming at learning from previous software projects to improve the development of new ones. In the last years, a considerable amount of research papers have been published reporting findings based on data mined from GitHub. As the community continues to deepen in its understanding of software engineering thanks to the analysis performed on this platform, we believe that it is worthwhile to reflect on how research papers have addressed the task of mining GitHub and what findings they have reported. Objective: The main objective of this paper is to identify the quantity, topic, and empirical methods of research works, targeting the analysis of how software development practices are influenced by the use of a distributed social coding platform like GitHub. Method: A systematic mapping study was conducted with four research questions and assessed 80 publications from 2009 to 2016. Results: Most works focused on the interaction around coding-related tasks and project communities. We also identified some concerns about how reliable were these results based on the fact that, overall, papers used small data sets and poor sampling techniques, employed a scarce variety of methodologies and/or were hard to replicate. Conclusions: This paper attested the high activity of research work around the field of Open Source collaboration, especially in the software domain, revealed a set of shortcomings and proposed some actions to mitigate them. We hope that this paper can also create the basis for additional studies on other collaborative activities (like book writing for instance) that are also moving to GitHub.
Overview
The claims and statistics of this paper haven’t been checked yet.
Free: it reads the open-access text and checks the first 5 claims that cite a source we can check. Create a free account to check every claim.
Integrity signals
Registry
Cites
Statistics
Verification
Claims the paper makes
The claims and statistics of this paper haven’t been checked yet.
Free: it reads the open-access text and checks the first 5 claims that cite a source we can check. Create a free account to check every claim.
Self-check
Percentages, sums and reported differences re-computed from the paper’s own numbers.
The self-check needs the paper’s full text.
Citations
Cites
Systematic Mapping Studies in Software Engineering
Petersen, K., Feldt, R., Mujtaba, S., & Mattsson, M. (2008) · Electronic Workshops in Computing · doi:10.14236/ewic/ease2008.8 · Cited by 3,239 · cited 1×
“METHODOLOGY To perform our mapping study we followed a procedure inspired by previous works [5], [6].”
MethodSocial coding in GitHub: transparency and collaboration in an open software repository
Dabbish, L., Stuart, C., Tsay, J., & Herbsleb, J. (2012) · Proceedings of the ACM 2012 conference on Computer Supported Cooperative Work · doi:10.1145/2145204.2145396 · Cited by 999
An exploratory study of the pull-based software development model
Gousios, G., Pinzger, M., & Deursen, A. V. (2014) · Proceedings of the 36th International Conference on Software Engineering · doi:10.1145/2568225.2568260 · Cited by 628
Storey, M.-A., Zagalsky, A., Filho, F. F., Singer, L., & German, D. M. (2017) · IEEE Transactions on Software Engineering · doi:10.1109/tse.2016.2584053 · Cited by 221 · cited 6×
“Furthermore, distractions and interruptions from communication channels negatively impact developer productivity as well as geographic, cultural, and economic factors can pose barriers to participation through social channels [56].”
BackgroundInfluential
Research works printed but not linked: 94
- 10.1109/ISSRE.2013.6698918 · DOI · Paper page
- zhang, 2014, A exploratory study of @-mention in GitHub’s pull-requests, Proc APSEC, 343
- 10.1109/MSR.2015.22 · DOI
- 10.1145/2441776.2441792 · DOI · Paper page
- 10.1145/2597073.2597113 · DOI
- 10.1109/ICSE.2015.55 · DOI · Paper page
- 10.1109/MSR.2015.42 · DOI · Paper page
- 10.1145/2786805.2786854 · DOI · Paper page
- 10.1145/2695664.2695856 · DOI
- tsay, 2014, Let’s talk about it: Evaluating contributions through discussion in GitHub, Proc FSE, 144
- 10.1145/2568225.2568315 · DOI · Paper page
- 10.1109/ICPC.2016.7503718 · DOI · Paper page
- 10.1109/SANER.2016.68 · DOI
- 10.1007/s10664-015-9393-5 · DOI · Paper page
- 10.1145/2804360.2804366 · DOI
- 10.1109/ICSE.2013.6606588 · DOI · Paper page
- 10.1109/ICSE.2013.6606557 · DOI
- 10.1145/2491411.2491415 · DOI · Paper page
- 10.1145/2884781.2884826 · DOI · Paper page
- stanciulescu, 2015, Forked and integrated variants in an open-source firmware project, Proc ICS, 151
- 10.1145/2897659.2897663 · DOI
- 10.1109/ICSE.2015.74 · DOI
- 10.1007/978-3-662-45550-0_46 · doi:10.1007/978-3-662-45550-0_46
- 10.1109/IISA.2015.7388026 · doi:10.1109/iisa.2015.7388026
- 10.1109/BESC.2014.7059515 · DOI
- 10.1145/1882362.1882435 · DOI · Paper page
- 10.1145/2556420.2558863 · DOI
- 10.1016/j.infsof.2015.01.008 · DOI
- 10.1145/2788993.2789838 · doi:10.1145/2788993.2789838
- 10.1109/SANER.2016.27 · DOI
- 10.1145/2675133.2675284 · DOI
- 10.1080/01639269.2015.1062586 · doi:10.1080/01639269.2015.1062586
- 10.1007/s10664-016-9436-6 · DOI
- 10.5381/jot.2015.14.4.e1 · doi:10.5381/jot.2015.14.4.e1
- 10.1145/2597073.2597121 · DOI
- 10.1109/ICSME.2016.31 · DOI · Paper page
- 10.1109/SANER.2015.7081875 · DOI
- kikas, 2015, Issue dynamics in GitHub projects, Proc Int Conf Product-Focused Softw Process Improvement, 295, 10.1007/978-3-319-26844-6_22 · doi:10.1007/978-3-319-26844-6_22
- 10.1145/2875913.2875914 · DOI
- jarczyk, 2014, GitHub projects. Quality analysis of open-source software, Proc SocInfo, 80
- 10.1587/transinf.2015EDP7363 · DOI
- 10.1145/2597073.2597119 · doi:10.1145/2597073.2597119
- 10.1109/APSEC.2015.12 · DOI
- 10.1145/2597073.2597118 · DOI · Paper page
- 10.1145/2597073.2597117 · DOI · Paper page
- junior, 2014, Using formal concept analysis to study social coding in GitHub, Proc MSR, 1
- 10.1109/IEEM.2015.7385840 · DOI
- 10.1109/IWESEP.2016.19 · DOI
- 10.1109/CHASE.2015.9 · DOI
- 10.2197/ipsjjip.24.339 · DOI
- 10.1142/S0219525914500246 · DOI
- 10.1145/2597073.2597120 · DOI
- weber, 2014, What makes an open source code popular on GitHub?, Proc ICDMW, 851
- 10.1109/CHASE.2015.14 · DOI
- 10.1145/2702123.2702549 · DOI · Paper page
- 10.1007/978-1-4302-1834-0 · DOI
- 10.1109/MSR.2015.36 · DOI
- 10.1109/HICSS.2014.405 · DOI
- 10.1109/WI-IAT.2012.228 · DOI
- 10.1109/MSR.2015.26 · DOI · Paper page
- 10.1287/mnsc.1060.0560 · DOI · Paper page
- 10.1109/ICSM.2008.4658096 · DOI
- 10.1016/S0065-2458(06)69005-0 · DOI
- 10.1145/2597073.2597114 · DOI
- 10.1007/978-3-642-02032-2_15 · DOI
- 10.1145/2556420.2556483 · DOI
- amann, 2014, Software mining studies: Goals, approaches, artifacts, and replicability, LASER Summer School, 121
- 10.1145/2666539.2666571 · DOI
- 10.1145/1368088.1368115 · DOI
- cosentino, 2016, Findings from GitHub. Methods, datasets and limitations, Proc MSR, 137
- 10.1109/SocialCom.2013.35 · DOI · Paper page
- 10.1145/2089125.2089127 · DOI · Paper page
- 10.1109/CSMR.2013.41 · DOI · Paper page
- 10.1145/2568225.2568305 · DOI
- mergel, 2014, Introducing Open Collaboration in the Public Sector The Case of Social Coding on GitHub
- 10.1109/MS.2013.13 · DOI · Paper page
- 10.1145/2797433.2797476 · DOI
- 10.1109/ICSM.2015.7332512 · doi:10.1109/icsm.2015.7332512
- 10.1145/2487788.2487832 · DOI
- yu, 2014, Who should review this pull-request: Reviewer recommendation to expedite crowd collaboration, Proc APSEC, 1, 335
- 10.1109/CINE.2015.13 · DOI
- 10.1109/WCRE.2013.6671288 · DOI
- 10.1145/2666539.2666570 · DOI
- 10.1145/2441776.2441794 · DOI
- lima, 2014, Coding together at scale: GitHub as a collaborative social network, Proc ICWSM, 10
- 10.1145/2141512.2141583 · DOI
- 10.1109/MS.2012.172 · DOI · Paper page
- 10.1109/APSEC.2013.104 · doi:10.1109/apsec.2013.104
- 10.1109/MSR.2012.6224294 · DOI · Paper page
- xavier, 2014, Understanding the popularity of reporters and assignees in the GitHub, Proc SEKE, 484
- 10.1145/2492517.2492627 · DOI
- badashian, 2014, Involvement, contribution and influence in GitHub and StackOverflow, Proceedings of CSSE, 19
- 10.1145/2468356.2468381 · DOI
- blincoe, 2015, Understanding the popular users: Following, affiliation influence and leadership on GitHub, Proc IST, 70, 30
Cited by
What’s in a GitHub Star? Understanding Repository Starring Practices in a Social Coding Platform
Borges, H., & Tulio Valente, M. (2018) · Journal of Systems and Software · doi:10.1016/j.jss.2018.09.016 · Cited by 317
Security Weaknesses of Copilot-Generated Code in GitHub Projects: An Empirical Study
Fu, Y., Liang, P., Tahir, A., Li, Z., Shahin, M., Yu, J., & Chen, J. (2023) · arXiv · doi:10.48550/arxiv.2310.02059 · Cited by 75
“We used code snippets generated by Copilot on GitHub as our research object to analyze the relevant security weaknesses of Copilot.”
MethodGrimoireLab: A toolset for software development analytics
Dueñas, S., Cosentino, V., Gonzalez-Barahona, J. M., del Castillo San Felix, A., Izquierdo-Cortazar, D., Cañas-Díaz, L., & Pérez García-Plaza, A. (2021) · PeerJ Computer Science · doi:10.7717/peerj-cs.601 · Cited by 33
Self-citationChua, B. B., & Zhang, Y. (2020) · Australasian Journal of Information Systems · doi:10.3127/ajis.v24i0.1714 · Cited by 7
AgenticFlict: A Large-Scale Dataset of Merge Conflicts in AI Coding Agent Pull Requests on GitHub
Ogenrwot, D., & Businge, J. (2026) · Proceedings of the 3rd ACM International Conference on AI-Powered Software · doi:10.1145/3805760.3814923
Metadata
- Authors
- Cosentino, V., Canovas Izquierdo, J. L., & Cabot, J.
- Venue
- IEEE Access
- Published
- 2017
- Volume
- 5
- Pages
- 7173-7192
- ISSN
- 2169-3536 (ISSN-L)
- OpenAlex
- W2601908482
- Cited by
- 168
- References
- 4
- FWCI
- 18.08
- Type
- journal article
- Language
- en
- Open access
- gold
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
How to cite
Cite CoChat for the checks on this page, and the paper for its own findings.
- This page
- CoChat. (2026). Citation check: A Systematic Mapping Study of Software Development With GitHub. https://app.cochat.ai/papers/10.1109/access.2017.2682323
- The paper
- Cosentino, V., Canovas Izquierdo, J. L., & Cabot, J. (2017). A Systematic Mapping Study of Software Development With GitHub. IEEE Access. https://doi.org/10.1109/access.2017.2682323
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.