English (United Kingdom)

https://curated-unify.zendy.io/wp-json/zendy-region/v1/featured_content/oa?rat=en

https://curated-unify.zendy.io/wp-json/zendy-region/v1/highlighted_journal/

Global: Zendy Plus annual

Presents the access of premium content as premium feature

Premium Content

Presents the keyphrase highlighting as premium feature

Keyphrase Highlighting

Presents the summarisation as premium feature

Summarisation

Insights

Presents the pdf analysis as premium feature

PDF Analysis

Presents the zaia usage as premium feature

ZAIA

Global: Zendy Plus monthly

Global: Zendy Tools annual

Global: Zendy Tools monthly

Global: Zendy Free Plan

Popular adoption of third-party libraries for contemporary softwaredevelopment has led to the creation of large inter-dependency networks, wheresustainability issues of a single library can have widespread network effects.Maintainers of these libraries are often overworked, relying on thecontributions of volunteers to sustain these libraries. In this work, wemeasure contributions that are aligned with dependency changes, to understandwhere they come from (i.e., non-maintainer, client maintainer, librarymaintainer, and library and client maintainer), analyze whether they contributeto library dormancy (i.e., a lack of activity), and investigate thesimilarities between these contributions and developers' typical contributions.Hence, we leverage socio-technical techniques to measure thedependency-contribution congruence (DC congruence), i.e., the degree to whichcontributions align with dependencies. We conduct a large-scale empirical studyto measure the DC congruence for the NPM ecosystem using 1.7 million issues,970 thousand pull requests (PR), and over 5.3 million commits belonging to107,242 NPM packages. At the ecosystem level, we pinpoint in time peaks ofcongruence with dependency changes (i.e., 16% DC congruence score).Surprisingly, these contributions came from the ecosystem itself (i.e.,non-maintainers of either client and library). At the project level, we findthat DC congruence shares a statistically significant relationship with thelikelihood of a package becoming dormant. Finally, by comparing source code ofcontributions, we find that congruent contributions are statistically differentto typical contributions. Our work has implications to encourage and sustaincontributions, especially to support library maintainers that requiredependency changes.

Giving Back: Contributions Congruent to Library Dependency Changes in a Software Ecosystem