git-into-gsoc

Find the Google Summer of Code (GSoC) organizations that fit you, the repositories that merge newcomers' pull requests, and the beginner issues nobody has claimed, with the evidence for each.

Try it in your browser · Install it · Connect your AI assistant · Read the beginner guide

Every season, many first-timers end up in a project that stopped answering, under an issue three people already claimed, or with a proposal that reads like a hundred others. The information to avoid that exists. It is just scattered across the official GSoC site, hundreds of ideas pages, and thousands of issue threads.

git-into-gsoc reads those sources for you and answers the questions newcomers actually ask:

It reads GitHub, and GitLab for most checks. It never invents an organization, an issue, or a date.

Three ways to start

In your browser, with nothing to install

Answer four questions on the start page and get three organizations with the reasons they fit. The ranking is the terminal tool's own code running in your browser, on a snapshot of the official list, so your answers never leave the page. The first visit downloads about 8 MB. You can also browse every organization.

In your terminal, for the whole journey

On macOS, Linux, or Windows with WSL (Windows Subsystem for Linux):

curl -fsSL https://raw.githubusercontent.com/anandkaranubc/git-into-gsoc/main/install.sh | bash

On Windows PowerShell:

irm https://raw.githubusercontent.com/anandkaranubc/git-into-gsoc/main/install.ps1 | iex

You need only an internet connection. If Python is missing, the installer offers uv, a free tool that brings its own Python, and uv adds its folder to your shell's startup file. The installer says what it installs and connects every AI assistant it finds. The install guide has the other ways, a preview option, and how to update or remove it.

Already use uv or pipx? Install the package from PyPI, then connect your assistants:

uv tool install git-into-gsoc    # or: pipx install git-into-gsoc
git-into-gsoc setup

Then open a new terminal and run the command below. It asks four questions like the start page, with your GitHub username in place of your experience. Press Enter to skip any of them.

git-into-gsoc start

In your AI assistant

To add git-into-gsoc as a plugin that updates with your assistant, run one line. Plugins need uv to start the git-into-gsoc server, which your assistant talks to through MCP (the Model Context Protocol, the standard way AI assistants use outside tools). For Claude Code:

claude plugin install git-into-gsoc --marketplace anandkaranubc/git-into-gsoc

Use it in your AI assistant has the line for Codex, GitHub Copilot CLI, Gemini CLI, Antigravity, VS Code, Cursor, Windsurf, and Claude Desktop, and how to update or remove each one.

Then ask in your own words, for example: "I want to do Google Summer of Code. I know Python and like science. Where do I start?" The assistant answers from the same live data as the terminal and shows its sources.

One-click buttons add only the server, without the skill (the written guidance that teaches your assistant the GSoC journey). They need uv too, and each installs the newest release:

Related MCP server: OpenCollab MCP

From first look to first pull request

Each step is one command. The beginner guide explains every step and what to expect, and the website shows recorded runs of several of them.

OWNER/NAME and the numbers are placeholders for the repository and issue you choose. git-into-gsoc --help lists every command, and most take --output json for scripts.

Why you can trust what it says

• Evidence, not guesses. Organizations come from the official list and the public archive, and dates from the official site. Every ranked result says why it ranks where it does, and where that reason came from.

• Honest about limits. A fit says how well the work matches you, never your chance of being accepted. Dates for a year Google has not announced are labelled as estimates. Sources and limitations says what each source cannot tell you.

• Private by default. The tool reads only public data and never posts, comments, or opens anything for you. Your profile and progress stay in a file on your computer, and the tool sends no telemetry. The website counts page views without cookies. Privacy has the details.

• No shortcuts. It will not mass-message maintainers, farm trivial pull requests, or write your proposal. It points you to each organization's AI policy and helps you do work you can explain.

How it compares

What we learned from other tools has the full comparison, with sources.

Where to go next

Help build it

git-into-gsoc is made for people taking their first steps in open source, and it is a good place to take one. Fixing a confusing sentence counts. So does reporting a command that did not work for you.

• Start with CONTRIBUTING.md. Setup takes a few minutes, and no previous open-source experience is needed.

• Look through the open issues. Ones labelled good first issue go quickly, so if none is free, a confusing sentence in the docs makes a fine first change.

• Read the architecture to see how the terminal tool, the assistant server, and the skill share one Python core.

If git-into-gsoc helped you, the most useful thing you can do is tell us what worked and what did not. It opens a public GitHub issue, so leave out anything private. Then tell a friend who is starting out.

License and disclaimer

MIT, see LICENSE.

This independent project is not affiliated with or endorsed by Google. Google Summer of Code and GSoC are trademarks of Google LLC. Always check dates, organizations, and rules on the official program site.