Papers › Evolving Collaboration, Dependencies, and Use in the Rust Open Source Software Ecosystem

Evolving Collaboration, Dependencies, and Use in the Rust Open Source Software Ecosystem

7 May 2022arXiv:2205.03597links table onlyarchive 2025-07-28

William Schueller, Johannes Wachs, Vito D. P. Servedio, Stefan Thurner, Vittorio Loreto

The archive published only this paper's code-link row. Authors, date and abstract are from arXiv's metadata (CC0), read from the Kaggle arXiv metadata snapshot of 2026-09-12 where its title matched the archive's; the title is the archive's.

Open-source software (OSS) is widely spread in industry, research, and government. OSS represents an effective development model because it harnesses the decentralized efforts of many developers in a way that scales. As OSS developers work independently on interdependent modules, they create a larger cohesive whole in the form of an ecosystem, leaving traces of their contributions and collaborations. Data harvested from these traces enable the study of large-scale decentralized collaborative work. We present curated data on the activity of tens of thousands of developers in the Rust ecosystem and the evolving dependencies between their libraries. The data covers seven years of developer contributions to Rust libraries and can be used to reconstruct the ecosystem's development history, such as growing developer collaboration networks or dependency networks. These are complemented by statistics on downloads and popularity, tracking the dynamics of use and success over time. Altogether the data give a comprehensive view of several dimensions of the ecosystem.

PaperPDFCode

Code

wschuell/repo_datasets officialmentioned in paper report

Repository list and official/mentioned flags are the archive's, frozen 2025-07-28. Reachability, where shown, is from one Syntology probe window (2026-09-16 to 2026-09-18); repositories not probed show nothing. GitHub stars are not tracked.

Code Syntology ran Syntology

Not run by Syntology. Nothing on this page verifies that the listed code works.

Results from the paper archive 2025-07-28

No leaderboard rows for this paper in the archive.

Report a problem or propose a change · a person checks every report against the paper or source before anything changes; decisions are listed on /corrections