Sponsor Ready
Free checklist for GitHub Sponsors readiness. Paste a public repo, get a ranked list of what's missing — no signup, nothing stored here.
Not sure what to paste? — it scores the project Sponsor Ready lives in, so you can see the checklist before pointing it at your own work.
Checking…
What this is and isn't
- Every check runs in your browser, calling GitHub's public API directly. This site has no server and stores nothing about the repos you check.
- This is an informational heuristic against publicly documented signals — it is not affiliated with GitHub and does not guarantee any sponsorship outcome. It never tells you to enable GitHub Sponsors.
- Only anonymous, aggregate usage counts (for example "a scan happened") may be recorded locally — never which repo you scanned.
Common questions
Does a high score mean GitHub will approve me for Sponsors?
No. This checklist has nothing to do with GitHub's own Sponsors program eligibility review — it scores publicly documented signals (a FUNDING.yml, a substantial README, recent activity, a license, and similar) that tend to correlate with a repo looking sponsor-ready to a human visitor. It never tells you to enable Sponsors and is not affiliated with GitHub. See all 10 signals ranked by weight, with the one-line fix for each. If you already use GitHub's own Community Standards page, here is how the two differ — this reads the same community-profile data and then asks a different question.
Why did my scan fail with a rate-limit error?
Every check calls GitHub's public API directly from your browser, unauthenticated, which GitHub caps at 60 requests per hour per visitor IP. If you or others on the same network have scanned several repos recently, wait a few minutes and try again — there is no server-side proxy here to work around the limit.
Can I check a private repository?
No. The tool only calls GitHub's public, unauthenticated API, so it can only see what an anonymous visitor to your repo page could see. A private repo returns a 404 and the checklist has no way to read it.
Does it store or send the name of the repo I scanned anywhere?
Your repo target is sent only to api.github.com, the same request your own browser would make visiting the repo page. This site has no server and stores nothing about which repos you check; only anonymous, aggregate usage counts like "a scan happened" may be recorded locally, with an opt-out below.
Can I share a link to a scan result?
Yes. After a scan, "Copy link to this result" puts the repo name in the page's own URL fragment (the part after #), which browsers never send to any server — opening the link just re-runs the same public scan in the recipient's own browser. It only works for public repos, so it never reveals anything that a visit to the repo's GitHub page would not already show.