Public Sponsor

Summary

Public Sponsor is an active, non-tiered GitHub profile achievement for sponsoring open-source work through GitHub Sponsors.

Trigger

Archived GitHub documentation directly states that sponsoring an open-source contributor through GitHub Sponsors awards the sponsor badge. GitHub’s Mars achievement announcement also identifies a badge for sponsoring open-source work through GitHub Sponsors.

Progression or tiers

Public Sponsor is documented as a single-level badge. No official tier progression is published.

Eligibility conditions

• The sponsorship must be created through GitHub Sponsors.
• The recipient and sponsoring account must be eligible to use the programme.
• Billing, region, account state, and recipient status can prevent the sponsorship from completing.
• Visibility affects public verification and may affect presentation; this edge case remains under study.

Award timing

GitHub does not publish a fixed processing interval between sponsorship activation and profile-award visibility.

Verification

1. Confirm the sponsorship is active through GitHub Sponsors.
2. Record activation and first-visible-award dates without publishing payment details.
3. Record whether the sponsorship is public or private.
4. Redact billing information, addresses, transaction identifiers, and eligibility records.
5. Document cancellation or visibility-change outcomes separately.

Evidence status

• The broad sponsorship trigger is Official.
• Public/private visibility, cancellation, account-state, and processing behaviour remain Observed or Unknown until independently reproduced.
• No official tiers are published.

Known limitations and edge cases

• Private sponsorships may prevent public verification.
• Cancellation, payment failure, recipient suspension, or programme exit can change visible state.
• Organisation and personal sponsorships may expose different controls.
• Billing records are sensitive and must not be submitted as public evidence.

Responsible participation

Sponsor maintainers or organisations whose work you genuinely wish to support. Do not create circular, coordinated, or misleading transactions for badge testing.

History

GitHub introduced the sponsor badge before the broader achievements system and later presented it alongside the Mars and Arctic profile badges.

References

• Archived GitHub profile documentation
• Open source goes to Mars
• Sponsoring an open-source contributor
• Managing your sponsorship

Last verified

19 July 2026. Scope: official broad trigger, current Sponsors controls, privacy obligations, and unresolved visibility and processing edge cases.

Back to the achievement index