Ecosystems in GitHub and a Method for Ecosystem Identification Using Reference Coupling
Open accessThe DOI matches its Crossref record.
Abstract
Software projects are not developed in isolation. Recent research has shifted to studying software ecosystems, communities of projects that depend on each other and are developed together. However, identifying technical dependencies at the ecosystem level can be challenging. In this paper, we propose a new method, known as reference coupling, for detecting technical dependencies between projects. The method establishes dependencies through user-specified cross-references between projects. We use our method to identify ecosystems in GitHub-hosted projects, and we identify several characteristics of the identified ecosystems. We find that most ecosystems are centered around one project and are interconnected with other ecosystems. The predominant type of ecosystems are those that develop tools to support software development. We also found that the project owners' social behaviour aligns well with the technical dependencies within the ecosystem, but project contributors' social behaviour does not align with these dependencies. We conclude with a discussion on future research that is enabled by our reference coupling method.
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
Cited by
An empirical comparison of dependency network evolution in seven software packaging ecosystems
Decan, A., Mens, T., & Grosjean, P. (2019) · Empirical Software Engineering · doi:10.1007/s10664-017-9589-y · Cited by 259
The sky is not the limit: multitasking across GitHub projects
Vasilescu, B., Blincoe, K., Xuan, Q., Casalnuovo, C., Damian, D., Devanbu, P., & Filkov, V. (2016) · Proceedings of the 38th International Conference on Software Engineering · doi:10.1145/2884781.2884875 · Cited by 77
“Such repositories are conceptually and technically related, or even interdependent [7].”
BackgroundSelf-citationCommitted to Trust: A Qualitative Study on Security & Trust in Open Source Software Projects
Wermke, D., Wöhler, N., Klemmer, J. H., Fourné, M., Acar, Y., & Fahl, S. (2022) · 2022 IEEE Symposium on Security and Privacy (SP) · doi:10.1109/sp46214.2022.9833686 · Cited by 42
“Blincoe et al. proposed a new method, reference coupling , for detecting technical dependencies between projects, finding that most ecosystems are centered around one project and are interconnected with other ecosystems [96].”
MethodModeling interconnected social and technical risks in open source software ecosystems
Schueller, W., & Wachs, J. (2024) · Collective Intelligence · doi:10.1177/26339137241231912 · Cited by 13
Metadata
- Authors
- Blincoe, K., Harrison, F., & Damian, D.
- Venue
- 2015 IEEE/ACM 12th Working Conference on Mining Software Repositories
- Publisher
- IEEE
- Published
- 2015-05
- Pages
- 202-211
- OpenAlex
- W4233214837
- Cited by
- 43
- References
- 0
- FWCI
- 4.97
- Type
- conference paper
- Language
- en
- Open access
- green
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: Ecosystems in GitHub and a Method for Ecosystem Identification Using Reference Coupling. https://app.cochat.ai/papers/10.1109/msr.2015.26
- The paper
- Blincoe, K., Harrison, F., & Damian, D. (2015). Ecosystems in GitHub and a Method for Ecosystem Identification Using Reference Coupling. 2015 IEEE/ACM 12th Working Conference on Mining Software Repositories. https://doi.org/10.1109/msr.2015.26
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.