🔎 GitHub Profile Reverse Lookup

🎯 Find any developer on GitHub using just an email, a name, or a partial username — instantly turn fragments of identity into verified developer profiles.

This scraper takes lists of emails, full names, or username fragments and returns the matching GitHub profiles with rich metadata: username, user ID, avatar, bio, company, location, public email, repository counts, follower stats, social links, and more. Perfect for OSINT, recruiting, lead enrichment, due diligence, and developer research.

🚀 What Does It Do?

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 Is This For?

🏢 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

✨ Features

• 📧 Email-to-Profile Resolution — The single most valuable lookup direction on GitHub
• 👤 Name & Username Search — Auto-detects what kind of input you provide
• 🔬 Commit Search Fallback — When the public user index fails, dig through public commits
• 🪪 Full Profile Enrichment — Bio, company, location, blog, Twitter, public email, hireable flag
• 📊 Activity Stats — Followers, following, public repos, public gists, account age
• 🏢 Optional Organization Filtering — Restrict to user accounts or include orgs
• 🎛️ Smart Filters — Mix emails, names, and fragments in one run; cap matches per query
• ⚡ Fast & Scalable — Process thousands of search terms per run with built-in rate limiting
• 🧹 Deduplication — Same login won't appear twice for the same search term
• 🔐 Token Support — Bring your own GitHub token for 5,000 req/h instead of 60
• 📤 Export Anywhere — Download results as JSON, CSV, Excel, or push to Google Sheets, Zapier, Make, or your CRM

🎛️ Filters & Options

Option	What It Does
🧩 Search Terms	Mixed list of emails, names, and usernames — the actor auto-detects each
📧 Emails	Force-classify entries as emails, bypassing auto-detection
👤 Full Names	Force-classify entries as display names
🔤 Username Fragments	Force-classify entries as partial GitHub logins
🔑 GitHub Token	Optional Personal Access Token — unlocks commit search and 80x higher rate limits
🔢 Max Results Per Query	How many matches to keep per search term — 1 for emails, 5–10 for names
🪪 Enrich Profile	Fetch full profile metadata for every match (bio, location, follower counts, etc.)
🏢 Include Organizations	Whether to also return GitHub organization accounts in results
🔬 Use Commit Search	Fall back to public commit history when an email isn't in the user index
⚙️ Max Concurrency	How many lookups to run in parallel
⏱️ Max Requests Per Minute	Hard ceiling on outbound GitHub API calls — keeps you under the rate limit
🌐 Proxy Configuration	Optional proxy settings — datacenter IPs are sufficient

📦 What You Get (Output Fields)

Every matched profile includes:

Identity

Field	Example
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

Profile

Field	Example
name	Brad Fitzpatrick
bio	https://bradfitz.com
email	brad@danga.com
company	Tailscale
location	Sunnyvale, CA
blog	https://bradfitz.com
twitterUsername	bradfitz
hireable	null

Activity Stats

Field	Example
publicRepos	247
publicGists	89
followers	5210
following	42
createdAt	2008-10-28T18:31:11Z
updatedAt	2026-04-22T08:12:33Z

Run Metadata

Field	Example
scrapedAt	2026-05-03T09:46:00.000Z
error	null

📊 Example Output

{
    "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
}

📋 Dataset Views

The Apify Console gives you 3 ready-made table views to quickly browse your results:

View	What It Shows
📊 Overview	Search term, username, user ID, name, company, location, profile URL, avatar
🎯 Lead Generation	Search term, username, name, public email, company, location, website, Twitter, hireable
📈 Activity Stats	Username, public repos, public gists, followers, following, account age

❓ 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 Custom Filters or Features?

I'm happy to customize this scraper for your specific needs! 🤝

Whether you need:

• 🎯 Additional filters (filter by minimum followers, account age, location, language, repository topics)
• 📊 Extra data fields or custom output formats (e.g. pinned repos, top languages, recent activity)
• 🔄 Integration with your CRM, Google Sheets, or database
• ⏰ Scheduled scraping with automatic deduplication and incremental enrichment
• 🌐 Cross-referencing with other developer platforms (GitLab, Bitbucket, Stack Overflow, LinkedIn) alongside GitHub

👉 Don't hesitate to reach out via private message — I respond quickly and I'm always open to building exactly what you need. No request is too small or too specific!

⚖️ Legal & Ethical Use

This scraper collects only publicly available information from GitHub. It does not access private repositories, hidden emails, authenticated content, or bypass any access controls. Please use the data responsibly and in compliance with applicable laws, GitHub's Terms of Service, and privacy regulations such as GDPR and CCPA.