✦Platform · How it works

From an open issue to a merged pull request.

Three moves: find work that is really open, know which season you are in, keep the record yourself. No resume upload, no onboarding call.

Step 01Find work that is open

Start from what is actually open.

One place to search public GitHub data: 40k open issues from 290 repositories, 8.8k archived program projects in the 12 program records, and 364 organizations with a profile of their own. Filter it, then open the thread on GitHub before you start work.

Behind the scenes

  • Issues crawled from 290 active repositories on 2026-10-21
  • Beginner-labelled work surfaced separately (757 issues)
  • Every repository page shows the README, guidelines and open work
  • Organization pages carry their program history and flagship repos
  • GitHub stays the source of truth - each row links to the live thread

Your action

Search by language, label or organization. Nothing needs an account, and every result links straight to GitHub.

Project archive

Ranked by stars, straight from the catalog

1ECC271k stars · 340 open issues · JavaScript
2hermes-agent250.7k stars · 48.4k open issues · Python
3the-book-of-secret-knowledge247.6k stars · 172 open issues · Other
4deepseek-harness242.6k stars · 0 open issues · TypeScript
5n8n206.5k stars · 1.1k open issues · TypeScript
Step 02Know the season

Work the calendar, not the guesswork.

13 funded or mentored programs are tracked with their published application, selection and coding windows, and the organizations tied to them. The archive of accepted projects from the last five years tells you what those orgs actually shipped.

Behind the scenes

  • Program pages list stipends, windows and participating orgs
  • Accepted-project archive lets you read a real proposal before writing one
  • Organization profiles show which programs a project has joined
  • Read-only public data: no tokens, no private repositories

Your action

Pick the season you are aiming at and read two or three accepted projects from the org you want.

Program windows

Live status on the contributor calendar

1googleGoogle Summer of CodeApplications close April
2outreachyOutreachyDec cohort pairing opens Nov
3linuxfoundationLFX MentorshipTerm 3 running now · Sep – Nov
4eclipse-foundationEclipse SoCRuns May – August
5MLHMLH FellowshipFall batch in session
githubgithubgooglegooglelinuxfoundationlinuxfoundationhuggingfacehuggingfacevercelvercelcloudflarecloudflare
Step 03Ship and keep the record

One board, four stages.

The board is yours: the issues you take move through Saved, Interested, Working on it and Completed, and the repositories you follow sit next to them with their stars, open issues and last update. It is stored in your browser first, and mirrored to your account only when you sign in.

Behind the scenes

  • Paste a GitHub issue URL and it is tracked with its live title and labels
  • Issues untouched for 90 days are flagged before you commit an evening
  • The overview page tells you what needs you, derived from your own rows
  • Export or delete everything the board remembers, from Settings
  • Nothing is ever claimed on your behalf - assignments stay GitHub's to confirm

Your action

Track one issue today and advance it when you open the pull request. The board keeps the dates; GitHub keeps the record.

Your board

The four stages every tracked issue sits in

1SavedOn the list. Nothing committed yet.
2InterestedYou have read the thread and mean to take it.
3Working on itA branch exists; the pull request is open or about to be.
4CompletedMerged, closed or handed back. The record stays.

That is the whole method - find, season, ship. The data behind each step is documented on the features and trust pages, and 364 organizations are profiled today.

✦The companies behind the index

The data comes from teams that ship at scale.

Every org profile, star count and program record on cyrus is pulled from the public GitHub footprint of organizations like these - then re-verified on a schedule.