1. GitHub user search Open on GitHub →

2. Google X-ray search Open in Google →

Reaches words GitHub's search ignores, such as a profile README or a framework named in a bio. Results are partial and can be months old.

3. The same search, ranked by recent work

StarHunt reads the repositories behind each profile, ranks people on what they shipped in the last twelve months, and shows the email or LinkedIn they chose to publish.

Run it in StarHunt →

3 free searches, no credit card needed.

What each part of the GitHub query does

GitHub's user search accepts a handful of qualifiers. The builder combines them; this is what each one matches, and where it misleads.

QualifierWhat it matches
type:userPeople only, not organisations.
language:goPeople who own repositories in that language. A framework is not a language, so React, Vue or Angular fall back to JavaScript or TypeScript.
location:"Berlin"The free-text location on the profile, as typed. "Berlin" does not match "Deutschland" or an empty field.
followers:>=10A floor on followers. Useful against empty accounts, not as a measure of skill.
repos:>=5A floor on public repositories, forks included.
created:<2022-01-01Accounts opened before a date. Account age says little about seniority.

The method around these queries, starting from the repositories that define a technology rather than from profiles, is in how to find developers on GitHub. Once you have a list, reading each profile is where the real filtering happens.

Where profile search stops

Every result above matches how people describe themselves and what languages they own. None of it says whether they are still building: a profile with a city and the right language can belong to someone who stopped committing three years ago, and GitHub sorts them alongside the people shipping every week.

That gap is what StarHunt fills. It maps the reference repositories of each technology, ranks the people who contribute to them on recent work, and normalises locations to metro areas, so "SF", "Bay Area" and "San Francisco, CA" count as one place. The search box above takes the same request in plain English.

Frequently asked questions

Can you filter GitHub users by a framework like React?

Not directly. GitHub's user search filters on the languages of the repositories a person owns, so React narrows to JavaScript or TypeScript. To target the framework itself, use the Google search this page writes, or start from the contributors of the framework's own repositories.

How do you sort GitHub user search results?

By best match, followers, repositories or join date, from the sort menu on the results page. There is no sort by recent activity, which is the signal that matters most when hiring.

What does the followers filter tell you about a developer?

Reach, not skill. Followers come from talks, posts and popular projects. A minimum of a few followers removes empty accounts; a high minimum mostly removes people who ship without promoting it.

Does GitHub user search show who is active right now?

No. It matches profile fields and repository languages, whatever the date of the last commit. Open each profile to check recent activity, or use a tool that ranks on it.