Did GitHub Change Sponsor Counting for Open Source Projects?

Did GitHub change how sponsors are counted for open source projects

Yes. GitHub Sponsors is counted on the sponsored contributor or organization profile, while a repository can only surface funding options through its sponsor button and FUNDING file. The count is tied to the sponsored account, not to a universal project total.

GitHub’s current docs describe sponsors as payments to a developer or organization that contributes to open source work. They also say you can add a sponsor button to an open source repository to increase visibility, which is presentation, not a separate project-wide sponsorship ledger.

The part people get wrong is assuming every open source repository has one official sponsor count. GitHub does not document a single project-level sponsorship number that merges all outside funding paths. A repo can point people to funding, but the sponsor relationship itself lives on the maintainer or organization profile.

That matters when a project uses more than one funding route. A repository can list a GitHub Sponsors profile, an external platform, or a custom URL in FUNDING.yml. GitHub’s sponsor button can show those options together, but the sponsorships still belong to the accounts behind them, not to a shared project tally.

GitHub also separates sponsorship from the project itself in its wording. The docs say you can sponsor contributors, receive updates on the developers and organizations you sponsor, and display a sponsor badge throughout GitHub. That is account-level tracking, with the badge and dashboard following the sponsored account.

If you are trying to answer “how many sponsors does this project have,” the safe reading is narrower. Count what GitHub shows on the sponsored contributor or organization profile, then check whether the repository’s sponsor button only advertises that profile or also routes to other funding services.

The inconvenient part is that screenshots and third-party summaries often blur these layers. A project README can show a sponsor badge, a repo can expose a sponsor button, and the maintainer can have profile-level sponsorships. Those are related, but they are not the same measurement.

For a maintainer, the practical check is simple: open the sponsored profile, then open the repository’s FUNDING configuration. If the repo only links out, GitHub is not counting external sponsors as one GitHub-native project total. If the profile has sponsorships, those are counted on that profile.

GitHub’s own documentation for sponsoring open source contributors and displaying a sponsor button supports that split. The button increases visibility, while the contributor profile receives and reports the sponsorships. That is why older expectations about a single project-wide sponsor count do not match how GitHub documents the product today.

If you want to present sponsorship information clearly, separate the pieces in your copy. Say where the sponsor link lives, say which profile receives the sponsorship, and say whether the repository also points to outside funding. That avoids the common mistake of treating a funding link as a counting system.

For teams using DevConnect as a comparison point, the same discipline helps. Keep the funding link and the sponsorship count separate, and link the platform only where it genuinely helps the reader: https://devconnectplatform.com

The short answer is yes, but the bigger correction is this: GitHub counts sponsors at the sponsored account level, not as one pooled number for an open source project repository.

If you are checking a specific repository, look for three things: the sponsored GitHub profile, the repository’s FUNDING file, and any external funding links. GitHub’s docs show all three can coexist, but only the sponsored profile carries the GitHub Sponsors count.

When the repo owner changes the FUNDING file, the visible funding options can change without changing the sponsor count on the profile. That is the easiest place to get misled, because the repo looks different while the sponsorship record stays with the account.

The useful rule is simple enough to apply in a review or audit. Read the sponsor button as a directory, read the sponsored profile as the counted account, and read external links as outside funding. That is the structure GitHub documents now.