pith. sign in

arxiv: 2604.03846 · v1 · submitted 2026-04-04 · 💻 cs.SE

Mapping GitHub Sponsorships: A Longitudinal Observatory for Open-Source Sustainability

Rylan Hiltz , Taher A. Ghaleb This is my paper

Pith reviewed 2026-05-13 16:52 UTC · model grok-4.3

classification 💻 cs.SE
keywords GitHub Sponsorsopen source fundingsponsorship networkgraph traversaldata observatorysustainability metrics
0
0 comments X

The pith

A continuously running observatory tracks the GitHub Sponsors network through priority-based graph traversal and daily incremental updates.

A machine-rendered reading of the paper's core claim, the machinery that carries it, and where it could break.

The paper introduces a live observatory to overcome the absence of bulk API access for studying financial support in open-source projects. It collects sponsorship data by traversing the network of sponsors and sponsored users, updates the dataset each day, normalizes values in real time, and makes results available through an interactive dashboard plus downloadable CSV files. A 72-hour sample run produced records for more than 49,000 users spread across 144 countries and already shows uneven participation and geographic clustering. The tool is positioned as an ongoing resource rather than a one-time snapshot, enabling ongoing exploration of funding patterns by researchers and practitioners.

Core claim

The central claim is that a priority-based graph traversal system with daily incremental updates and real-time normalization can build and maintain a comprehensive, analysis-ready dataset of the GitHub Sponsors ecosystem and expose it through a public dashboard and CSV exports.

What carries the argument

Priority-based graph traversal with daily incremental updates and real-time normalization, which systematically follows sponsorship links while respecting API constraints to assemble the network.

If this is right

  • Researchers gain access to regularly refreshed data for studying how sponsorships relate to project activity and survival.
  • The dashboard supports filtering by country, demographics, and funding status to spot patterns in who receives support.
  • Exported CSV files allow direct statistical analysis of asymmetries in participation and geographic concentration.
  • Practitioners can benchmark their own sponsorship levels against the broader population of funded developers.

Where Pith is reading between the lines

These are editorial extensions of the paper, not claims the author makes directly.

  • The same traversal technique could be extended to other platforms that lack bulk funding data, such as Patreon or Open Collective.
  • Over multiple years the accumulated dataset could reveal whether sponsorship growth tracks changes in project maintenance or contributor numbers.
  • Observed geographic concentration raises the question of whether targeted outreach could broaden the base of sponsors in underrepresented regions.

Load-bearing premise

The traversal method can reach and record the large majority of active sponsorship relationships without significant omissions caused by rate limits or incomplete public visibility.

What would settle it

A side-by-side comparison that finds the observatory dataset omits a large share of verifiable sponsorships or shows persistent gaps after repeated daily runs would show the traversal is incomplete.

Figures

Figures reproduced from arXiv: 2604.03846 by Rylan Hiltz, Taher A. Ghaleb.

Figure 1
Figure 1. Figure 1: illustrates the workflow of the longitudinal observatory collector. The observatory traverses the GitHub Sponsors network using a queue, starting from Sponsorable users and iteratively ex￾ploring sponsorship relationships. Users are dequeued and checked for staleness; stale users are re-enqueued. For each user, the sys￾tem checks database presence, fetches profile and activity data if needed, and updates t… view at source ↗
read the original abstract

Financial sustainability is vital for open-source software, yet systematic research on funding remains limited. GitHub Sponsors, launched in 2019 as a direct developer-to-developer funding model, lacks bulk API access, hindering large-scale studies. This paper introduces a live, continuously operating observatory for tracking and analyzing the GitHub Sponsors ecosystem. The observatory performs priority-based graph traversal with daily incremental updates, real-time normalization, and exposes collected data through an interactive dashboard and analysis-ready CSV exports. A sample dataset collected during a 72-hour run captures 49K+ users across 144 countries and serves as an example of the tool's output, not a fixed deliverable. An interactive dashboard (https://github-sponsorships.com) enables practitioners and researchers to explore sponsorship patterns, filter by geography and demographics, and benchmark against funded peers. Preliminary results on the sample show strong participation asymmetries and geographic concentration, suggesting several research directions.

Editorial analysis

A structured set of objections, weighed in public.

Desk editor's note, referee report, simulated authors' rebuttal, and a circularity audit. Tearing a paper down is the easy half of reading it; the pith above is the substance, this is the friction.

Referee Report

1 major / 2 minor

Summary. The paper introduces a continuously operating observatory for the GitHub Sponsors ecosystem that performs priority-based graph traversal with daily incremental updates and real-time normalization. It exposes the collected data via an interactive dashboard and analysis-ready CSV exports. A 72-hour sample run is presented, capturing over 49,000 users across 144 countries, which illustrates participation asymmetries and geographic concentration but is explicitly positioned as an example output rather than a fixed dataset.

Significance. If the data-collection pipeline operates as described, the work provides a valuable public resource for studying open-source financial sustainability, addressing the gap created by GitHub's lack of bulk API access. The dashboard and CSV exports lower barriers for practitioners and researchers to explore sponsorship patterns, while the sample data demonstrates the tool's potential to surface empirical patterns in funding distribution.

major comments (1)
  1. [Abstract] Abstract and data-collection description: the priority-based graph traversal is presented as the core mechanism for mapping the Sponsors network, yet no pseudocode, rate-limit handling strategy, estimated population size, or coverage metric (e.g., fraction of known sponsors recovered) is supplied. This omission makes it impossible to assess whether the 49K+ user sample is comprehensive or systematically biased by API constraints and visibility gaps.
minor comments (2)
  1. [Abstract] The phrase 'real-time normalization' during a 72-hour collection window should be clarified, as it could be interpreted as continuous processing versus post-collection batch normalization.
  2. [Abstract] The manuscript would benefit from an explicit statement of the total number of sponsorship edges collected in the sample, in addition to the user count, to better characterize the dataset scale.

Simulated Author's Rebuttal

1 responses · 0 unresolved

We thank the referee for the constructive feedback and positive recommendation for minor revision. We agree that additional technical details on the data-collection pipeline will strengthen the manuscript and enable better evaluation of the sample's representativeness.

read point-by-point responses

  1. Referee: [Abstract] Abstract and data-collection description: the priority-based graph traversal is presented as the core mechanism for mapping the Sponsors network, yet no pseudocode, rate-limit handling strategy, estimated population size, or coverage metric (e.g., fraction of known sponsors recovered) is supplied. This omission makes it impossible to assess whether the 49K+ user sample is comprehensive or systematically biased by API constraints and visibility gaps.

    Authors: We agree that the abstract and data-collection description would benefit from greater technical specificity. In the revised manuscript we will add: (1) pseudocode for the priority-based graph traversal algorithm, (2) a description of our rate-limit handling strategy (token rotation, exponential backoff, and daily incremental updates), and (3) a dedicated subsection discussing potential biases, visibility gaps, and our mitigation approach. Because GitHub provides no official population total or ground-truth sponsor list, we cannot compute a precise coverage fraction; however, we will report the traversal starting set, observed growth rate, and qualitative assessment of reach based on known high-visibility sponsors. revision: yes

Circularity Check

0 steps flagged

No circularity; purely descriptive tool and data-collection paper

full rationale

The manuscript introduces an observatory tool that performs priority-based graph traversal to collect GitHub Sponsors data, with daily updates and dashboard export. No equations, fitted parameters, predictions, or derivations appear anywhere in the text. The central claim is the existence and operation of the tool itself plus a 72-hour sample; this does not reduce to any self-referential input or prior self-citation. The paper is self-contained against external benchmarks and contains no load-bearing steps that match the enumerated circularity patterns.

Axiom & Free-Parameter Ledger

0 free parameters · 1 axioms · 0 invented entities

The central claim rests on the assumption that GitHub's sponsorship relationships are sufficiently visible and traversable through available interfaces despite the acknowledged lack of bulk API access.

axioms (1)
  • domain assumption GitHub Sponsors relationships can be discovered via priority-based graph traversal without bulk API access
    Invoked in the description of the observatory's core data collection mechanism.

pith-pipeline@v0.9.0 · 5458 in / 1189 out tokens · 52808 ms · 2026-05-13T16:52:42.585292+00:00 · methodology

discussion (0)

Sign in with ORCID, Apple, or X to comment. Anyone can read and Pith papers without signing in.

Lean theorems connected to this paper

Citations machine-checked in the Pith Canon. Every link opens the source theorem in the public Lean library.

What do these tags mean?
matches
The paper's claim is directly supported by a theorem in the formal canon.
supports
The theorem supports part of the paper's argument, but the paper may add assumptions or extra steps.
extends
The paper goes beyond the formal theorem; the theorem is a base layer rather than the whole result.
uses
The paper appears to rely on the theorem as machinery.
contradicts
The paper's claim conflicts with a theorem or certificate in the canon.
unclear
Pith found a possible connection, but the passage is too broad, indirect, or ambiguous to say the theorem truly supports the claim.

Reference graph

Works this paper leans on

14 extracted references · 14 canonical work pages

  1. [1]

    Stefano Comino and Fabio M Manenti. 2011. Dual licensing in open source software markets.Information Economics and Policy23, 3-4 (2011), 234–242

    work page 2011

  2. [2]

    Annamaria Conti, Vansh Gupta, Jorge Guzman, and Maria P. Roche. 2023.Incen- tivizing Innovation in Open Source: Evidence from the GitHub Sponsors Program. Working Paper w31668. National Bureau of Economic Research, Cambridge, MA. http://www.nber.org/papers/w31668 Revised November 2023

    work page 2023

  3. [3]

    Youmei Fan, Tao Xiao, Hideaki Hata, Christoph Treude, and Kenichi Matsumoto

    work page

  4. [4]

    My GitHub Sponsors profile is live!

    “My GitHub Sponsors profile is live!” Investigating the Impact of Twitter/X Mentions on GitHub Sponsors. InProceedings of the IEEE/ACM 46th International Conference on Software Engineering. 1–12

    work page

  5. [5]

    Sean McGuire, Erin Schultz, Bimpe Ayoola, and Paul Ralph. 2023. Sustainability is stratified: Toward a better theory of sustainable software engineering. In IEEE/ACM 45th International Conference on Software Engineering. IEEE, 1996– 2008

    work page 2023

  6. [6]

    2023.Sponsorship funding in open-source software: Effort reallocation and spillover effects in knowledge-sharing ecosystems

    Poonacha K Medappa, Murat M Tunc, and Xitong Li. 2023.Sponsorship funding in open-source software: Effort reallocation and spillover effects in knowledge-sharing ecosystems. Technical Report. HEC Paris

    work page 2023

  7. [7]

    Cailean Osborne. 2024. Open Source Software Developers’ Views on Public and Private Funding: A Case Study on scikit-learn. InCompanion publication of the conference on computer-supported cooperative work and social computing. 154–161

    work page 2024

  8. [8]

    Cassandra Overney, Jens Meinicke, Christian Kästner, and Bogdan Vasilescu

    work page

  9. [9]

    In Proceedings of the ACM/IEEE 42nd international conference on software engineering

    How to not get rich: An empirical study of donations in open source. In Proceedings of the ACM/IEEE 42nd international conference on software engineering. 1209–1221

    work page

  10. [10]

    Naomichi Shimada, Tao Xiao, Hideaki Hata, Christoph Treude, and Kenichi Matsumoto. 2022. GitHub Sponsors: Exploring a New Way to Contribute to Open Source. InProceedings of the 44th International Conference on Software Engineering (ICSE ’22). ACM, New York, NY, USA, 12. doi:10.1145/3510003.3510116

    work page doi:10.1145/3510003.3510116 2022

  11. [11]

    Mikko Valimaki. 2003. Dual licensing in open source software industry.Systemes dInformation et Management8, 1 (2003), 63–75

    work page 2003

  12. [12]

    Colin C Venters, Rafael Capilla, Elisa Yumi Nakagawa, Stefanie Betz, Birgit Penzenstadler, Tom Crick, and Ian Brooks. 2023. Sustainable software engineering: Reflections on advances in research and practice.Information and Software Technology164 (2023), 107316

    work page 2023

  13. [13]

    Yaxin Wang, Liang Wang, Hao Hu, Jing Jiang, Hongyu Kuang, and Xianping Tao

    work page

  14. [14]

    In2022 IEEE 46th Annual Computers, Software, and Applications Conference (COMPSAC)

    The Influence of Sponsorship on Open-Source Software Developers’ Activ- ities on GitHub. In2022 IEEE 46th Annual Computers, Software, and Applications Conference (COMPSAC). IEEE, 924–933

    work page