Crawlsmith

GitHub Profile Reverse Fast Lookup

Find GitHub profiles from emails, full names, or username fragments. Returns enriched profile data — login, ID, avatar, bio, company, location, repo counts, and more.

What it does

This scraper automatically resolves identity fragments into real GitHub profiles and collects structured, ready-to-use data for every match. No manual searching, no copy-pasting — just feed it your list and download the results.

Three lookup modes — mix and match in a single run:

  1. Email Lookup — Find the GitHub account behind any email address. Works against the public user index and (with a token) the public commit history — the same trick recruiters and security researchers use to deanonymize developers.
  2. Name Lookup — Find every GitHub user matching a full name. Returns the top candidates so you can disambiguate by company or location.
  3. Username Fragment Lookup — Recover full handles from partial or remembered usernames.

Who uses it

Use Case How It Helps
OSINT Investigators Resolve emails to developer identities, cross-reference handles across platforms, build subject profiles
Recruiters & Sourcers Turn LinkedIn names or resume emails into GitHub portfolios with repo counts and tech footprint
B2B Sales & Lead Gen Enrich developer leads with public emails, company, location, and websites
Security Researchers Map breach-data emails to active GitHub identities, audit committer footprints
DevRel & Community Teams Find contributors, reach out to power users, build outreach lists
Due Diligence Analysts Validate that a person claiming to be a developer actually has a GitHub presence

Input

12 options. Required ones are marked.

Option What it does
Search Terms Mixed list of emails, full names, or username fragments.
Emails Optional list of email addresses to look up explicitly.
Full Names Optional list of full names to look up explicitly.
Username Fragments Optional list of username fragments or partial logins.
GitHub Token (optional) Personal Access Token (classic or fine-grained) for higher rate limits (5,000 req/h vs 60 unauthenticated) and access to commit search — which is the most reliable way to match an…
Max Results Per Query Maximum number of matching profiles returned per search term.
Enrich Profile Fetch full profile data (bio, company, location, public email, repo counts, follower counts, blog, Twitter handle, hireable flag, dates) for every match.
Include Organizations Also return organization accounts that match.
Use Commit Search for Emails When an email is not found in the public user index, fall back to searching public commits authored with that email.
Max Concurrency How many search terms to process in parallel.
Max Requests Per Minute Hard ceiling on outbound requests per minute.
Proxy Configuration Optional proxy settings.

Output fields

19 fields, grouped the way the dataset views show them. Export to JSON, CSV, Excel or pull them through the API.

Overview

  • Search Term
  • Type
  • Username
  • User ID
  • Name
  • Company
  • Location
  • Profile URL
  • Avatar

Lead Generation

  • Search Term
  • Username
  • Name
  • Public Email
  • Company
  • Location
  • Website
  • Twitter
  • Hireable
  • Profile URL

Activity Stats

  • Username
  • Public Repos
  • Public Gists
  • Followers
  • Following
  • Joined
  • Last Updated

Example output

One record, shortened. Real runs return one row like this per result.

{
  "searchTerm": "brad@danga.com",
  "searchType": "email",
  "matchSource": "search-commits",
  "username": "bradfitz",
  "userId": 2621,
  "userType": "User",
  "profileUrl": "https://github.com/bradfitz",
  "avatarUrl": "https://avatars.githubusercontent.com/u/2621?v=4",
  "name": "Brad Fitzpatrick",
  "bio": "https://bradfitz.com",
  "email": "brad@danga.com",
  "company": "Tailscale",
  "location": "Sunnyvale, CA",
  "blog": "https://bradfitz.com",
  "twitterUsername": "bradfitz",
  "hireable": null,
  "publicRepos": 247,
  "publicGists": 89,
  "followers": 5210,
  "following": 42,
  "createdAt": "2008-10-28T18:31:11Z",
  "updatedAt": "2026-04-22T08:12:33Z",
  "scrapedAt": "2026-05-03T09:46:00.000Z",
  "error": null
}

How to run it

  1. 1. Open the scraper on Apify and sign in (free plan works).
  2. 2. Fill in the input: search terms, URLs or filters, and a result limit.
  3. 3. Run it, then download JSON, CSV or Excel, or pull the dataset through the API.
  4. 4. Schedule it to get fresh data daily or weekly.

FAQ

How can the scraper find a GitHub user from just an email? +

GitHub exposes two public surfaces tying emails to users: the user search index (when a developer has set their email to public) and the commit history (any email used to author a public commit is searchable). With a token, this scraper queries both — that's why it works even when the email is not on the user's profile page.

Do I need a GitHub token? +

For occasional lookups, no — GitHub allows 60 unauthenticated requests per hour and ~10 search calls per minute. For batch jobs or commit-based email lookups, yes — a free Personal Access Token raises this to 5,000 requests per hour.

What if the email is not found? +

The actor returns a record with error: "No GitHub profile found..." so you can clearly distinguish "no match" from "lookup failed". Names and username fragments rarely return zero results.

Can I export the data? +

Yes — JSON, CSV, Excel, XML, HTML, RSS. You can also push data directly to Google Sheets, Zapier, Make, or any webhook/API endpoint.

How often should I run this? +

Profile data changes slowly. Re-run weekly or monthly to refresh stats (followers, repos), or whenever you have a new batch of emails or names to resolve.

Does it work with proxies? +

Yes — datacenter proxies work fine. GitHub does not require residential IPs. Proxies are mostly useful for splitting unauthenticated rate limits across multiple IPs.

Can it find private profiles or hidden emails? +

No. The scraper only reads publicly-accessible information. It does not bypass authentication, scrape login-walled pages, or access GitHub's private data.

Need something this scraper does not do?

Extra fields, a different filter, a recurring feed into your database or a one-off bulk export.

Ask for a custom version

Related scrapers