Open Source Funding Needs Better Data, Not Another Thank-You Campaign

Open-source maintainers are regularly thanked for keeping the internet running. Gratitude is not a financing model. Thousands of businesses depend on packages maintained by individuals or small teams, yet funding decisions are often disconnected from actual dependency risk and operational value.

A 2026 research project introduced a continuously updated observatory for GitHub Sponsors. Its sample captured tens of thousands of users across more than one hundred countries and found strong participation asymmetries and geographic concentration. The project is useful not because it produces one final ranking, but because it creates infrastructure for asking better questions over time.

Visibility is uneven before funding begins

Maintainers with large audiences, recognizable personal brands, or highly visible projects are more likely to attract sponsors. Essential libraries that operate quietly inside other tools may receive less attention even when their failure would affect far more organizations.

This creates a familiar market problem: funding follows what is easy to see, while infrastructure risk accumulates in less visible layers. A company may sponsor a popular framework and still ignore the smaller parser, build tool, or security library that its product directly depends on.

Companies should fund from the dependency graph

A more responsible process starts with inventory. Organizations should know which open-source packages are used in production, who maintains them, how frequently they release, whether critical issues remain unresolved, and whether the project has a credible succession path.

Funding can then be connected to business impact:

• Direct sponsorship for critical maintainers.
• Paid maintenance or security work.
• Engineering time contributed upstream.
• Shared funding pools for foundational dependencies.
• Procurement rules that include open-source sustainability.

Data must not become a popularity contest

An observatory can reveal patterns, but a dashboard cannot determine who “deserves” support. Maintainers have different goals, legal structures, costs, and community expectations. Some projects need money; others need documentation help, governance support, infrastructure, or relief from issue triage.

The value of better data is accountability. It allows a company to compare what it says about open source with what it actually invests. It also helps researchers examine whether funding reaches different regions, project sizes, and kinds of technical work.

Open-source sustainability will not be solved by a single platform feature. It improves when companies treat dependencies as part of their supply chain and maintainers as infrastructure partners rather than an unlimited source of free labor.