The American Journal of Engineering and Technology
63
https://www.theamericanjournals.com/index.php/tajet
TYPE
Original Research
PAGE NO.
63-70
10.37547/tajet/Volume07Issue08-07
OPEN ACCESS
SUBMITED
15 July 2025
ACCEPTED
28 July 2025
PUBLISHED
10 August 2025
VOLUME
Vol.07 Issue 08 2025
CITATION
Karen Sarkisyan. (2025). The Role of Open-Source Contributions in the
Development of the Frontend Ecosystem. The American Journal of
Engineering and Technology, 7(8), 63
–
70.
https://doi.org/10.37547/tajet/Volume07Issue08-07
COPYRIGHT
© 2025 Original content from this work may be used under the terms
of the creative commons attributes 4.0 License.
The Role of Open-Source
Contributions in the
Development of the
Frontend Ecosystem
Karen Sarkisyan
Senior Software Engineer at EPAM Systems, Inc Belgrade, Serbia
Abstract:
This paper examines how open source helps
shape the frontend world by pointing out its part in fast-
tracking progress and setting uniform client-side web
standards. Its importance comes from massive growth
—
more than 5.2 billion actions on GitHub and over 2.5
million packages on npm
—the community’s move
toward TypeScript, and React's supremacy. This work
tries to define a broader model of open source help that
covers not just code but also CI/CD setups, plugins,
translated docs, and even meetup groups, while
checking how this affects the lifecycle of frontend tools
plus standards. What makes this work new is bringing
together info from GitHub Octoverse, npm Registry,
corporate OSPO reports using a method unifying
descriptive stats, types of contributions, network
analysis on pull-request workflows, assessment of
ecosystem strength through bus-factor measures, as
well as maintainer burnout metrics. The proposed three-
tier participation model
—
individual maintainers,
corporate contributors, and institutional bodies (OpenJS
Foundation, TC39)
—
enables the description of
mechanisms for idea generation, resource scaling, and
API standardization. Key findings demonstrate that open
source contributions deliver unprecedented speed and
flexibility in adopting innovations: the median pull-
request merge time is 9 hours, large-scale events such
as Hacktoberfest attract tens of thousands of
newcomers, and the “Vite + Vitest + Storybook”
toolchain sets the DevEx standard, enhancing the
network effect of package publication and consumption.
It also exposes systemic risks: 60% of maintainers are
burned out, and 65% of projects have a low bus factor
—
sustainable funding, OSPO initiatives, and mentorship
programs for maintaining ecosystem health. This article
The American Journal of Engineering and Technology
64
https://www.theamericanjournals.com/index.php/tajet
will help OSS project leaders, DevEx specialists, and
OSPO teams strategize long-term support and scaling for
open frontend tools.
Keywords:
open source, contribution, frontend
ecosystem, GitHub, npm, maintainers, OSPO, DevEx,
resilience, standardization.
Introduction
Over the past decade, the evolution in client-side web
technologies has been unprecedented. In 2024 alone,
more than 5.2 billion contributions were recorded
across 518 million repositories on GitHub, encompassing
public OSS projects and private corporate forks [1]. This
growth has been accompanied by an exponential
expansion of the npm registry, which by May 2025 hosts
over 2.5 million packages and services approximately 30
billion downloads each month, making it the largest
code repository in the world [2]. A significant qualitative
shift is noted in a recent survey [3], where 67% of
respondents reported writing more TypeScript than
“vanilla” JavaScript, reflecting the community’s move
toward stronger typing and improved application
scalability.
The driving force behind this dynamic is open-source
contribution. Core frontend libraries are distributed
under permissive licenses, engaging thousands of
developers: the flagship React package is downloaded
over 38 million times each week [4], and according to
one study [5], roughly 70% of frontend specialists use it,
rendering React a de facto industry standard. Every pull
request
—
whether it fixes a bug, adds tests, or improves
documentation
—
triggers a chain reaction of updates in
dependent packages and lowers the entry barrier for
newcomers, accelerating the diffusion of technologies
throughout the stack
—
from bundlers to UI frameworks.
In this study, “open source contribution” is defined as
any publicly tracked contribution to a project distributed
according to the Open Source Definition formulated by
the Open Source Initiative
—
be it source-code
modifications, CI/CD configurations, new bundler
plugins, documentation translations, or the organization
of educational meetups [6]. This broad perspective
reflects the multidisciplinary nature of modern frontend
development. It emphasizes that a project’s value arises
from lines of code and the collective knowledge
formalized in transparent workflows.
Materials and Methodology
This research analyzes 28 sources, including public
activity metrics (GitHub Octoverse, npm Registry),
industry developer surveys, corporate OSPO reports,
technical documentation of key tools, and the Open
Source Initiative’s definition of open source soft
ware.
The theoretical foundation comprises data on
contribution volumes and package counts: the
Octoverse 2024 report documented 5.2 billion events
across 518 million repositories [1], while npm registry
analysis confirmed over 2.5 million packages and
roughly 30 billion monthly downloads [2], illustrating the
interdependence between ecosystem growth and
community engagement. The State of JavaScript survey
indicated that 67 % of frontend engineers have migrated
to TypeScript, altering contribution paradigms and
codebase quality [3]. The concept of open source
contribution was extended based on the Open Source
Definition to include not only code changes but also
CI/CD configurations, plugins, translations, and meetup
organization [6].
Studies of institutional OSS support mechanisms enrich
the epistemological context: Google’s OSPO report
notes that about 10 % of Alphabet employees regularly
contribute to public repositories, and the OpenJS
Foundation’s Ecosystem Sustainability Program grants
secure library ver
sions [10, 11]. Public, “living”
WHATWG standards for HTML and the Edge Runtime
specification in Next.js exemplify the convergence of
contribution practice with Web API standardization
processes [12, 13]. A case study analysis of
Hacktoberfest demonstrated how large-scale initiatives
engage newcomers
—
almost 98,000 participants in 2023
versus 676 at its inception
—
creating initial entry points
into OSS projects [18].
Methodologically,
the
work
combines
several
approaches. First, descriptive statistics quantified
commit, PR, and issue volumes on GitHub and the
number of npm packages with downloads from 2022 to
2025 [1, 2]. Second, contributions were classified by
type (code, CI/CD, plugins, translations, meetups) using
OSI criteria and data from popular packages such as
React, Vite, Vitest, and Storybook [4, 15
–
17]. Third,
comparative trend analysis of GitHub and npm revealed
correlations between package growth and developer
activity, accounting for migration to TypeScript [3, 9].
Fourth, content and network analysis of pull-request
processes and RFC mechanisms in React and Vue
repositories assessed merge speed (median nine hours),
contributor participation, and public roadmaps [19
–
22].
Finally, ecosystem resilience was evaluated through bus-
The American Journal of Engineering and Technology
65
https://www.theamericanjournals.com/index.php/tajet
factor and maintainer burnout metrics, alongside
analyses of corporate sponsors and grant volumes
(GitHub Sponsors, Linux Foundation, and SonarSource
surveys) [24
–
28].
Historical Overview
From the advent of jQuery in 2006 to the present, the
frontend ecosystem has undergone a marked status
shift: jQuery remains the most widespread scripting
solution
—
serving 73.8% of all sites tracked by
W3Techs
—
but the actual focal point for developers has
moved to single-page frameworks [7]. In the latest
popularity survey [8], React holds a 39.5% share among
developers, Angular 17.1%, Vue 15.4%, and the nascent
Svelte has already reached 6.5%. The historical changes
in market share are presented in Table 1.
Table 1. Front-End Framework Trends: Popularity, Desire & Admiration [8]
Year
React.js/React
Angular
Vue.js
AngularJS/Ang
ular.js
Svelte
2018
27,8
36,9
N/A
N/A
N/A
2019
31,3
30,7
15,2
30,7
N/A
2020
35,9
25,1
17,3
16,1
N/A
2021
40,14
22,96
18,97
11,49
2,75
2022
42,62
20,39
18,82
8,99
4,58
2023
40,58
17,46
16,38
7,21
6,62
2024
39,5
17,1
15,4
6,8
6,5
The Role of Infrastructure and Contributors
The growing complexity of client applications and the
need for universal state management and SSR have
rendered the architectural patterns of React and Vue de
facto standards. In contrast, jQuery has become
entrenched in the long tail of CMS platforms and
corporate portals. Simultaneously, the infrastructure
services landscape has expanded: npm now hosts over
two million packages and handles tens of billions of
downloads weekly, becoming the primary conduit for
frontend innovation [9].
Three complementary participation models sustain such
explosive growth. Individual maintainers
—
from John
Resig in the jQuery era to Rich Harris (Svelte) and Evan
You (Vue)
—
remain the source of radical ideas and rapid
prototypes, with their engagement often setting project
cadences.
Corporate
contributors
amplify
this
momentum through resources: the Google OSPO report
notes that approximately 10% of Alphabet employees
regularly contribute to open source, having delivered
over 7,000 code elements in five years [10]. Above these
layers operate institutional bodies: the OpenJS
Foundation oversees dozens of key projects
—
from
Node.js to Jest
—
and in 2024
–
2025 launched its
Ecosystem Sustainability Program to provide long-term
funding for secure releases and support of legacy library
versions [11]. This three-tier model lowers the bus
factor,
distributes
review
workloads
between
volunteers and commercial teams, and furnishes
strategic lifecycle management for tools.
The foundation of this cooperation remains the open
standardization process of the Web. The TC39 working
group maintains a public repository with dozens of
active Stage 2+ proposals, where each language
enhancement proceeds via pull requests, and
framework
contributors
regularly
author
specifications
—
recent
Decorators
and
Temporal
features emerged directly from library needs. WHATWG
publishes “living” HTML and DOM standards on GitHub;
the current HTML Living Standard was updated on 16
May 2025, and every merge reflects the consensus of
browser vendors and the community [12]. Coordination
between the OpenJS Foundation and these bodies
streamlines the transition of experimental APIs from
projects such as Node.js or Fastify into official
specifications, closing the loop: from prototype
contribution to mass adoption in the package registry,
The American Journal of Engineering and Technology
66
https://www.theamericanjournals.com/index.php/tajet
and finally to core platform standards.
The rapid growth of the frontend ecosystem relies
primarily on the infrastructural “springs” of the previous
decade: the GitHub social platform and the npm
registry. Concurrently, npm has become the main
channel for delivering innovation, making code reuse
more economically advantageous than authoring from
scratch [2].
At the architectural level, micro-frontends have been
one of the recent years' most striking yet ambivalent
phenomena. According to survey data [5], the
proportion of teams adopting this approach fell from
75.4% in 2022 to 23.6% in 2024, indicating a
reassessment
of
the
complexity
inherent
in
orchestrating independent mini-SPAs and a shift of
interest toward simpler meta-frameworks and mono
repo solutions (Fig. 1).
Fig. 1. What micro-frontend solution have you used? [5]
Simultaneously, edge rendering has gained popularity:
Edge Runtime executes middleware by default in
Next.js, allowing part of the application logic to move
closer to CDN nodes, thereby reducing time-to-first-byte
latency without needing a separate server cluster [13].
The Rise of Generative AI in Development
A second primary vector is the automation of
development processes via generative AI assistants. The
study [14], based on GitHub Copilot telemetry, shows
that 91% of teams already merge pull requests
containing AI-generated code into their central
repositories, and developers accept about 30% of
Copilot’s suggestions,
indicative of a mature balance
between trust and critical review. Tech companies and
startups lead in Copilot adoption (70
–
75%), suggestion
usage (35%), paid licenses (90%), and reported
productivity gains (15
–
25%); banks and industrial firms
exhibit moderate metrics (55
–
65% adoption, 20
–
30%
usage, 60
–
80% licensing, 10
–
20% gains); healthcare and
insurance are the most cautious (50
–
60% adoption, 25%
usage, 70
–
80% licensing, 5
–
15% gains). Across all
sectors, features such as code completion, bug fixes (10
–
15%), and refactoring (5
–
10%) are actively employed, as
shown in Fig. 2.
The American Journal of Engineering and Technology
67
https://www.theamericanjournals.com/index.php/tajet
Fig. 2. GitHub Copilot Adoption Metrics by Industry [14]
The “Vite + Vitest + Storybook” toolchain is a catalyst for
widespread adoption of new practices, which defines
the benchmark developer experience. The Vite bundler
is downloaded over 27 million times per week [15], the
Vitest test runner over 11 million [16], and Storybook
around 6.4 million [17]; these metrics ensure that new
projects are likely to begin with a modern stack and
thereby inherit best practices in performance and
modularity out of the box. These drivers generate a
positive network effect: the low cost of package
publishing, ease of contribution, and high degree of
automation make open contribution a rational strategy
for individual developers and corporate teams, thus
accelerating further ecosystem saturation.
The Pull-Request Model and Ecosystem Growth
The rapid frontend development cycle is materialized
primar
ily through GitHub’s pull
-request model, which
has become the universal protocol for change
consensus. Large-scale events such as Hacktoberfest
further stress this contribution “artery”. In October
2023, nearly 98,000 participants participated compared
to 676 at its launch, yielding tens of thousands of minor
fixes and serving as an initial entry point for newcomers
[18].
To prevent such a dense flow of changes from causing
regressions, most public repositories integrate
automated CI/CD pipelines. In 2024, 10.54 billion CPU-
minutes of GitHub Actions were executed
—
a nearly
one-third increase over the previous year; Octoverse
notes that teams automate testing and linting [1]. The
rapid feedback loop “PR → automated runs → preview”
has become a technical prerequisite for edge rendering
and “preview” domains, which platforms like Vercel and
Netlify deploy in seconds, transforming every merge
request into an independent test environment.
When changes affect a framework’s public API,
developers switch to a formalized RFC process. The
React repository currently has around forty open
proposals, supported by 137 discussion-bearing
commits [19]. In contrast, Vue has 26 active and 157
closed RFCs, demonstrating genuine community
engagement and enabling core teams to filter out risky
ideas before implementation begins [20]. Public
roadmaps maintained via GitHub Projects complement
this practice by allowing contributors to synchronize
their efforts with release windows and plan migrations
of dependent packages in advance, thus reducing
ecosystem integration overhead.
Non-Code Contributions and Community Engagement
An equally significant layer of contribution is formed
around non-code artifacts. The Vue framework
exemplifies this in practice: its official documentation
has been translated into 14 languages
—
including
Korean, Bengali, and Persian
—
thanks to a distributed
network of volunteer translators who submit PRs by the
exact mechanism as code changes [21]. This is
The American Journal of Engineering and Technology
68
https://www.theamericanjournals.com/index.php/tajet
augmented by mentorship discussions in Issues and
dedicated Discord channels, where experienced
maintainers assist newcomers in refining patches
—
this
“social wrapper” transforms disparate edits into a
managed stream of value for the entire frontend
ecosystem.
The open nature of contributions yields an unusually
dense innovation cycle, establishing a historically
maximal pace for the evolution of frontend tools. Owing
to the pull-request model, this flow materializes in rapid
releases: the median active-developer PR is merged just
9 hours after submission, reducing the time between
idea and feature availability to nearly a single work shift
[22]. When such changes extend beyond a specific
project, they serve as a proving ground for future
standards: the typical TC39 proposal pathway from
Stage 0 to Stage 4 may take years
—
sometimes up to a
decade
—
but
live
polyfills
and
reference
implementations in OSS enable developers to adopt new
APIs long before their official inclusion in ECMAScript
[23]. This way, open repositories shrink the lag between
experiment and de jure specification, accelerating
practice diffusion across the platform.
Quantitative surveys confirm the low barrier to entry.
According to a Linux Foundation study, 53% of “super
-
maintainers” have implemente
d formal processes for
onboarding new contributors, thereby systematizing
knowledge transfer and creating an internal talent
pipeline for projects [24]. Thus, the open model not only
reproduces code but also sustainably prepares the next
generation of developers.
Sustainability Challenges in Open Source
However, the model has its drawbacks. A Tidelift survey
reports that nearly 60% of maintainers have either
ceased work on projects or seriously considered doing
so due to burnout and overload [25]. Bus-factor
statistics are equally concerning: 65% of popular GitHub
projects have a critical core of two or fewer individuals,
meaning the loss of a single contributor can paralyze the
evolution of a framework or tool [26]. Resource
asymmetry exacerbates these risks: as noted earlier,
only
one
corporation
—
Alphabet
—
reports
that
approximately 10% of its full-time employees regularly
contribute to OSS, resulting in an imbalance of influence
between large companies and individual contributors
[10]. Consequently, the strategic roadmaps of key
frameworks (e.g., React, whose core is entirely funded
by Meta) may shift toward the priorities of major
employers, leaving the community as observers rather
than equal authors. These challenges make sustainable
funding, distributed review, and mentorship programs
not a luxury but a prerequisite for the continued health
of the frontend ecosystem.
Strategic Solutions to Support the Ecosystem
Meaningful contribution begins with selecting tasks that
benefit the project, not merely quantitative PR growth,
but genuine technical debt reduction. Developers
should seek tickets labeled good first issue or help
wanted, write automated tests, and improve
documentation: these changes undergo faster review
and yield visible results. Companies whose products are
dominated by third-party JavaScript dependencies
should consider OSS funding as an element of
operational risk. According to a 2024 corporate survey,
organizations worldwide already invest over USD 7.7
billion in open projects
—
primarily through the labor of
in-house engineers [27]
—
yet this investment is
unevenly distributed: GitHub Sponsors has transferred
only about USD 40 million to contributors, less than 0.5%
of the market’s estimated value [28]. Direct
compensation for maintainers increases an ecosystem's
resilience: paid maintainers perform critical security and
support tasks significantly more often than volunteers
[25]. An internal OSPO team coordinating the selection
of dependencies, sponsorship budgets, and employee
participation in public RFCs is effective governance.
Foundations, universities, and educational programs fill
the gaps left by the market. First, they can scale
mentoring: in contexts where most maintainers have
abandoned or nearly abandoned projects due to
burnout,
systematic
mentor
–
junior
pairs
help
redistribute review workloads. Second, grants and
competitions for translation and localization
—
leveraging community events like Hacktoberfest
—
make
projects accessible to contributors in regions where
English is not the working language. Finally, joint courses
on modern stacks
—
Vite, Storybook, Vitest
—
convert
DevEx best practices into educational case studies, thus
replenishing the ecosystem with a new generation of
contributors. Such three-way partnerships among
developers, industry, and institutions reduce risk
concentration, accelerate innovation adoption, and
cement the open model as the primary mechanism of
frontend progress.
In conclusion, the open contribution model offers the
frontend community unparalleled speed and agility:
The American Journal of Engineering and Technology
69
https://www.theamericanjournals.com/index.php/tajet
from ultra-fast pull-request merges to pre-release API
and reference implementation access. At the same time,
structured onboarding, grants and educational support,
corporate involvement via OSPOs, and direct funding
help fight burnout and out-of-hand maintainer
reliance
—
in turn enabling a gooddevs-industry-
academia balance not just to speed up taking on new
ideas but also building strong bases for future standards
and spreading best practices all across frontend-land.
Conclusion
This study confirms that open source contributions are
the main driver of the extraordinary growth and
evolution of the frontend ecosystem. The magnitude
and speed of updates seen on GitHub and NPM lately
have been possible due to an open collaborative process
that guarantees the fast diffusion of tech innovations
and backing for mission-critical stack parts, from UI
libraries to automation tools. Every contribution,
whether a pull request fixing a bug or a documentation
translation, triggers a chain reaction of updates across
dependent projects and lowers barriers for new
participants, thereby accelerating the propagation of
best practices throughout the stack.
A significant reason this dynamic stays resilient is its
three-tier contribution model: individual maintainers
produce new ideas and set the speed for prototyping;
corporate groups add resources and scaling know-how;
and institutional units
—
like the OpenJS Foundation or
the TC39 working group
—
offer strategic coordination
and standardization. Such levels of coordination are
shared in the assessment and evolution duties that bring
scientific advancement (e.g., new APIs) into the official
language and platform guidelines.
In addition to the clear benefits of the open contribution
model, systemic risks have been noted: very high rates
of maintainer burnout, low bus factor in many popular
projects, and resource asymmetry between the
community and large corporations. These issues require
specific actions on sustainable code funding, enlarged
mentorship programs, and supported educational
initiatives. In particular, establishing and enhancing
OSPO teams within companies, direct sponsorship of
maintainers, and grant- and academic-level programs
can mitigate pressure on ecosystem “bottlenecks” and
improve overall resilience.
This is how the open contribution model bestows upon
the frontend community unique agility and speed in
adopting innovations. Of course, its long-term viability
will depend on a balanced interplay among developers,
industry, and academic institutions. That harmonious
combination of technical, organizational, and financial
mechanisms will preserve development momentum as
an underpinning for future standards, sustainability, and
scalability for the frontend ecosystem.
References
“Octoverse: AI leads Python to top lang
uage as the
number of global developers surges,”
The GitHub Blog
,
Oct.
29,
2024.
insights/octoverse/octoverse-2024
2025).
Coders Stop, “I Downloaded 10,000 NPM Packages and
Found Something Disturbing,”
JavaScript in Plain
English
,
May
08,
2025.
“State of JavaScript 2024: Usage,”
Stateofjs
, 2024.
https://2024.stateofjs.com/en-US/usage
18, 2025).
“react,”
npm
https://www.npmjs.com/package/react
(accessed Apr. 19, 2025).
A. Dąbrowska, “State of Frontend 2024,”
The Software
House
, 2024.
https://tsh.io/state-of-frontend
Apr. 20, 2025).
Open Source Initiative, “The Open Source Definition,”
Open
Source
Initiative
,
Feb.
16,
2024.
“Usage statistics and market share of jQuery for
websites,”
w3techs
https://w3techs.com/technologies/details/js-jquery
(accessed Apr. 21, 2025).
“Front
-
end
frameworks
popularity,”
Gist
https://gist.github.com/tkrotoff/b1caa4c3a185629299
ec234d2314e190
D. Pinckney, F. Cassano, A. Guha, and J. Bell, “A Large
Scale Analysis of Semantic Versioning in NPM,”
arXiv
(Cornell
University)
,
Jan.
2023,
doi:
https://doi.org/10.48550/arxiv.2304.00394
S. Vargas, “2023 Open Source Contributions: A Year in
Review,”
Open
Source
Blog
,
2023.
https://opensource.googleblog.com/2024/08/2023-
open-source-contribution-report.html
23, 2025).
The American Journal of Engineering and Technology
70
https://www.theamericanjournals.com/index.php/tajet
“Announcing the Ecosystem Sustainability Program
(ESP) with HeroDevs as the First Partner,”
OpenJS
Foundation
,
May
21,
2024.
https://openjsf.org/blog/ecosystem-sustainability-
program
“HTML Living Standard,”
Whatwg
, May 16, 2025.
https://html.spec.whatwg.org/multipage/
(accessed
May 17, 2025).
“API
Reference:
Edge
Runtime,”
Next.js
https://nextjs.org/docs/app/api-reference/edge
(accessed Apr. 24, 2025).
V. Vasudevan, “Github Copilot Adoption Trends: Insights
from
Real
Data,”
Opsera
https://www.opsera.io/blog/github-copilot-adoption-
trends-insights-from-real-data
“vite,”
npm
,
Mar.
14,
2025.
https://www.npmjs.com/package/vite
26, 2025).
“vitest,”
npm
https://www.npmjs.com/package/vitest
(accessed Apr. 26, 2025).
“storybook,”
npm
https://www.npmjs.com/package/storybook
Apr. 26, 2025).
S. R. Moon, “Hacktoberfest 2024: Contributing to Open
Source and Growing as a Developer,”
DEV Community
,
Oct.
20,
2024.
“Reactjs/rfcs,”
GitHub
https://github.com/reactjs/rfcs
(accessed Apr. 27, 2025).
vuejs, “Pull requests · vuejs/rfcs,”
GitHub
, Jan. 19, 2025.
https://github.com/vuejs/rfcs/pulls
2025).
“Vue.js
-
Translations,”
Vuejs.org
https://vuejs.org/translations/
“The median developer’s PRs take 14 hours to merge,”
Graphite
https://graphite.dev/research/median-time-
S. V. de Sá Lucena, “ECMAScript standardization
process,”
Medium
,
Jun.
28,
2019.
https://sergioviniciuss.medium.com/ecmascript-
standardization-process-94a64acf771f
01, 2025).
A. Salkever, “Open Source Maintainers,” The Linux
Foundation, Jul. 2023. Accessed: May 03, 2025. [Online].
Available:
Sonar, “Maintainer burnout is real. Almost 60% of
maintainers have quit or considered quitting
maintaining one of their projects,”
SonarSource
, May 25,
2023.
https://www.sonarsource.com/blog/maintainer-
“Bus factor of top GitHub projects,”
Metabase
, 2022.
https://www.metabase.com/blog/bus-factor
May 05, 2025).
S. Boysel
et al.
, “2024 Open Source Software Fund
ing
Report,”
Open source funding survey 2024
, Nov. 19,
2024.
https://opensourcefundingsurvey2024.com/
(accessed May 06, 2025).
“GitHub
Sponsors,”
GitHub
