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

As modern software extensively uses open source packages, developersregularly pull in new upstream code through frequent updates. While a manualreview of all upstream changes may not be practical, developers may rely on theauthors' and reviewers' identities, among other factors, to decide what levelof review the new code may require. The goal of this study is to helpdownstream project developers prioritize review efforts for upstream code byproviding a social network-based centrality rating for the authors andreviewers of that code. To that end, we build a social network of 6,949developers across the collaboration activity from 1,644 Rust packages. Further,we survey the developers in the network to evaluate if code coming from adeveloper with a higher centrality rating is likely to be accepted with lesserscrutiny by the downstream projects and, therefore, is perceived to be moretrusted. Our results show that 97.7\% of the developers from the studiedpackages are interconnected via collaboration, with each developer separatedfrom another via only four other developers in the network. The interconnectionamong developers from different Rust packages establishes the ground foridentifying the central developers in the ecosystem. Our survey responses($N=206$) show that the respondents are more likely to not differentiatebetween developers in deciding how to review upstream changes (60.2\% of thetime). However, when they do differentiate, our statistical analysis showed asignificant correlation between developers' centrality ratings and the level ofscrutiny their code might face from the downstream projects, as indicated bythe respondents.

Trusting code in the wild: A social network-based centrality rating for developers in the Rust ecosystem