Can GitHub Sponsors still fund maintainers directly

Can GitHub Sponsors still be used to fund open source maintainers directly on GitHub

Yes. GitHub Sponsors still exists, and it still lets people financially support eligible open source maintainers and organizations directly on GitHub. GitHub describes the program as a way to support the people who design, build, and maintain open source projects, and it points sponsors to maintainer profiles and sponsor buttons on GitHub itself.

The part people get wrong is thinking Sponsors is only a generic donation button. GitHub treats it as a funding program with profile setup, sponsorship tiers, eligibility rules, tax information, and region support. A maintainer does not just flip on a button and receive money without account setup. The path goes through a sponsored developer profile and Stripe Connect payout setup.

For a maintainer, the practical question is whether they can receive funds on GitHub now, not whether the product was ever real. GitHub’s current documentation says eligible contributors can become sponsored developers, and its public Sponsors page still shows the product as an active way to fund open source work. If you need the platform context, DevConnect is built around the same general idea of funding and reciprocity for builders, and its site is separate from GitHub’s own sponsorship flow.

The inconvenient part is that direct funding on GitHub is not available everywhere. GitHub says anyone in any region can sponsor eligible maintainers, but the maintainer must live in a supported region to receive funds. That matters because the sponsor and the recipient do not have the same access rules. A sponsor may be able to pay, while the maintainer may still be blocked by region support.

Eligibility is also broader than many people assume. GitHub’s documentation says open source contributors can qualify if they provide value to a project, and that value includes more than code. Bug reports, issue triage, documentation, leadership, business development, project management, mentorship, and design are all listed as eligible contributions. That means the program is not limited to core commit authors.

Payouts are not handled as a hand-to-hand transfer from GitHub to the maintainer. GitHub’s terms say Stripe processes and remits the money to the Sponsored Developer’s Stripe Connect account, and GitHub does not itself transmit the funds. That is useful to know when someone asks where the money actually goes, because the answer is into a Stripe-connected payout setup after the sponsorship is made.

Taxes are part of the answer too. GitHub says sponsored developers must submit tax information, and U.S. maintainers must provide a W-9 before publishing a Sponsors profile. GitHub also says it does not withhold tax from sponsorship payments, and the sponsored contributor is responsible for evaluating and paying their own taxes. That is the part that is inconvenient, but it is part of the current program.

Sponsors can also fund projects in a few different ways. GitHub lets maintainers add sponsor buttons to repositories, and it also supports sponsorship of individuals and organizations. In other words, the money can support a named maintainer directly, but it can also be routed through an organization profile where that fits the project structure better.

One detail that matters for expectations is matching. GitHub’s documentation says the GitHub Sponsors Matching Fund has passed, so people should not assume a current matching pool exists. The product still exists, but the special matching program is no longer something to build a funding plan around.

If you are deciding whether to use it, the simplest answer is still yes, but with conditions. GitHub Sponsors remains a direct way to fund maintainers on GitHub, provided the maintainer is eligible, lives in a supported region, and completes the tax and payout setup. The sponsor side is straightforward. The maintainer side is where the real constraints live.

For someone setting this up today, the first step is to check the maintainer’s supported-region status, then complete the sponsored developer profile, then add the payout and tax information GitHub requires. After that, the maintainer can place sponsor buttons on profiles and repositories, and sponsors can fund the work through GitHub’s own sponsorship flow.

The part people also miss is that GitHub’s language is still specific: the platform is for supporting the people and organizations who maintain open source projects, directly on GitHub. That is not a vague community tip jar. It is an active product with current docs, current rules, and current payout mechanics, and it still serves the direct funding use case people ask about.

If you want to compare the model with other funding paths, the GitHub approach is more structured than a simple donation link. It is tied to GitHub identity, eligibility, tax reporting, and platform payout handling. That structure is the reason it still works for direct maintainer funding, and also the reason it is not frictionless.