The DOI matches its Crossref record; 30 of the 30 references it cites were found in a registry or an index.
Do developers update their library dependencies?: An empirical study on the impact of security advisories on library migration
Open accessAbstract
Third-party library reuse has become common practice in contemporary software development, as it includes several benefits for developers. Library dependencies are constantly evolving, with newly added features and patches that fix bugs in older versions. To take full advantage of third-party reuse, developers should always keep up to date with the latest versions of their library dependencies. In this paper, we investigate the extent of which developers update their library dependencies. Specifically, we conducted an empirical study on library migration that covers over 4,600 GitHub software projects and 2,700 library dependencies. Results show that although many of these systems rely heavily on dependencies, 81.5% of the studied systems still keep their outdated dependencies. In the case of updating a vulnerable dependency, the study reveals that affected developers are not likely to respond to a security advisory. Surveying these developers, we find that 69% of the interviewees claimed to be unaware of their vulnerable dependencies. Moreover, developers are not likely to prioritize a library update, as it is perceived to be extra workload and responsibility. This study concludes that even though third-party reuse is common practice, updating a dependency is not as common for many developers.
Overview
The claims and statistics of this paper haven’t been checked yet.
Run the check — free, no account needed. It reads the open-access text and checks the sources it cites.
Integrity signals
Registry
Cites
Statistics
Verification
Claims the paper makes
The claims and statistics of this paper haven’t been checked yet.
Run the check — free, no account needed. It reads the open-access text and checks the sources it cites.
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
Rogers, E. M., Singhal, A., & Quinlan, M. M. (2019) · An Integrated Approach to Communication Theory and Research · doi:10.4324/9780203710753-35 · Cited by 37,322
Valente, T. W. (2003) · Genetics in Medicine · doi:10.1097/01.gim.0000061743.67794.c4 · Cited by 13,723
Gluesing, J. C. (2012) · Leadership in Science and Technology: A Reference Handbook · doi:10.4135/9781412994231.n14 · Cited by 3,210
CCFinder: a multilinguistic token-based code clone detection system for large scale source code
Kamiya, T., Kusumoto, S., & Inoue, K. (2002) · IEEE Transactions on Software Engineering · doi:10.1109/tse.2002.1019480 · Cited by 1,711
Self-citationLaws of software evolution revisited
Lehman, M. M. (1996) · Lecture Notes in Computer Science · doi:10.1007/bfb0017737 · Cited by 572
An Empirical Study of API Stability and Adoption in the Android Ecosystem
McDonnell, T., Ray, B., & Kim, M. (2013) · 2013 IEEE International Conference on Software Maintenance · doi:10.1109/icsm.2013.18 · Cited by 304
Using origin analysis to detect merging and splitting of source code entities
Godfrey, M. W., & Zou, L. (2005) · IEEE Transactions on Software Engineering · doi:10.1109/tse.2005.28 · Cited by 248
Effect of violation of normality on the t test of the correlation coefficient.
Edgell, S. E., & Noon, S. M. (1984) · Psychological Bulletin · doi:10.1037//0033-2909.95.3.576 · Cited by 192
A look at the dynamics of the JavaScript package ecosystem
Wittern, E., Suter, P., & Rajagopalan, S. (2016) · International Conference on Mining Software Repositories (MSR) · doi:10.1145/2901739.2901743 · Cited by 167
How do developers react to API deprecation?
Robbes, R., Lungu, M. F., & Röthlisberger, D. (2012) · doi:10.1145/2393596.2393662 · Cited by 152
Cited by
(2018) · doi:10.1145/3180155.3180209 · Cited by 98
Technical leverage analysis in the Python ecosystem
Paramitha, R., & Massacci, F. (2023) · Empirical Software Engineering · doi:10.1007/s10664-023-10355-2 · Cited by 7
Metadata
- Authors
- Kula, R. G., German, D. M., Ouni, A., Ishio, T., & Inoue, K.
- Venue
- Empirical Software Engineering
- Published
- 2017-05-11
- Volume
- 23
- Issue
- 1
- Pages
- 384-417
- ISSN
- 1382-3256 (ISSN-L)
- 1573-7616
- OpenAlex
- W3121596715
- Cited by
- 351
- References
- 30
- FWCI
- 39.22
- Type
- journal article
- 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: Do developers update their library dependencies?: An empirical study on the impact of security advisories on library migration. https://app.cochat.ai/papers/10.1007/s10664-017-9521-5
- The paper
- Kula, R. G., German, D. M., Ouni, A., Ishio, T., & Inoue, K. (2018). Do developers update their library dependencies?: An empirical study on the impact of security advisories on library migration. Empirical Software Engineering. https://doi.org/10.1007/s10664-017-9521-5
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.