GitHub Developer Lead Finder & Email Enricher 🧑‍💻📧

Find developers on GitHub and turn them into outreach-ready leads — complete with verified emails, company, location, skills, and social links. Perfect for technical recruiters, DevRel teams, dev-tool founders, and B2B sales targeting developers.

Unlike profile-only GitHub scrapers, this Actor mines public commit history to surface real, contactable emails (the ones hidden from the profile page) and infers each developer's tech stack so you can segment by skill.

---

💡 What it does

Give it a search, and it returns a clean dataset of developer leads. Five ways to find people:

Search type	What you get
User search	Anyone matching a GitHub query — e.g. language:Rust location:Berlin followers:>100
Repository search	Contributors of repos matching a query — e.g. langchain stars:>500
Stargazers	Everyone who starred a repo (your competitor's repo = your warm leads)
Contributors	Everyone who committed to specific repos
Organization members	Public members of any GitHub org

Each lead is enriched with:

• ✅ Email — from the profile and mined from public commits (the high-value part)
• 🏢 Company, 📍 location, 📝 bio, and the "available for hire" flag
• 🧠 Top programming languages and total stars earned (skill & influence signal)
• 🔗 Twitter / X, personal website / blog, LinkedIn (when discoverable)
• 📊 Followers, following, public repos, account age

---

🚀 Quick start

1. Pick a Search type.
2. Fill the matching field:
   • User / Repository search → Search query
   • Stargazers / Contributors → Repositories (e.g. facebook/react)
   • Organization members → Organizations (e.g. vercel)
3. (Recommended) Paste a GitHub token to unlock 5,000 requests/hour.
4. Click Start.

Example: find hireable React-ecosystem developers in Europe

{
  "searchType": "users",
  "searchQuery": "language:JavaScript location:Germany followers:>200",
  "onlyHireable": true,
  "extractEmails": true,
  "maxItems": 300,
  "githubToken": "ghp_xxx"
}

Example: leads from a competitor's stargazers

{
  "searchType": "stargazers",
  "repositories": ["supabase/supabase"],
  "onlyWithEmail": true,
  "maxItems": 1000
}

---

📤 Output sample

{
  "username": "octodev",
  "name": "Octo Developer",
  "email": "octo@example.com",
  "emails": ["octo@example.com", "octo@work.io"],
  "company": "Acme Inc",
  "location": "Berlin, Germany",
  "bio": "Backend engineer. Go, Rust, distributed systems.",
  "hireable": true,
  "website": "https://octo.dev",
  "linkedin": null,
  "twitterUsername": "octodev",
  "followers": 842,
  "topLanguages": ["Go", "Rust", "TypeScript", "Python"],
  "totalStars": 5120,
  "publicRepos": 73,
  "githubUrl": "https://github.com/octodev",
  "scrapedAt": "2026-05-30T10:00:00.000Z"
}

Export to JSON, CSV, Excel, or via API — drop straight into your CRM, Clay table, or cold-email tool.

---

🔑 GitHub token (highly recommended)

Without a token GitHub allows only 60 requests/hour. With a free Personal Access Token you get 5,000/hour, so larger runs finish reliably.

1. Go to https://github.com/settings/tokens
2. Generate a token — no scopes are required for public data (classic or fine-grained both work).
3. Paste it into the GitHub token field. It's stored as a secret.

---

💰 Pricing (pay-per-event)

You only pay for results you receive:

Event	What it covers
Profile scraped	Each enriched developer profile delivered to your dataset
Email enriched	Charged only when a contactable email is actually found
Actor start	Apify's standard low start fee (covers run startup)

No subscription, no per-result charge when nothing is found.

---

⚙️ Options reference

Option	Default	Description
searchType	users	How to find developers (see table above)
searchQuery	—	GitHub search syntax (user/repository search)
repositories	—	owner/name list (stargazers/contributors)
organizations	—	Org logins (organization members)
maxItems	200	Max leads to return
extractEmails	true	Mine emails from profile + commit history
deepEmailSearch	false	Also scan owned-repo commits when no email is found (slower)
includeNoreplyEmails	false	Include anonymized @users.noreply.github.com addresses
enrichStats	true	Add top languages + total stars
onlyWithEmail	false	Keep only leads with an email
onlyHireable	false	Keep only developers open to work
minFollowers	0	Skip developers below this follower count
githubToken	—	Personal Access Token for higher rate limits

---

🧭 Use cases

• Technical recruiting — find hireable engineers by language, location, and influence.
• Dev-tool sales & DevRel — turn stargazers/contributors of relevant repos into a warm outreach list.
• Open-source intelligence — map who builds what across an ecosystem.
• Community building — identify active contributors to invite or sponsor.

---

❓ FAQ

Where do the emails come from? Git commits store the author's email, and GitHub exposes recent public commits via its API. This Actor reads those public commit records (and the profile email) and filters out non-contactable noreply addresses. Everything used is publicly available through GitHub's official API.

Why is email sometimes empty? Many developers commit using GitHub's privacy email or have no public activity. Enable deepEmailSearch for a more thorough scan, or set onlyWithEmail to keep only leads that have one.

Is this reliable at scale? Yes — it uses GitHub's official REST API (no fragile HTML scraping, no proxies), with automatic rate-limit handling and retries.

---

📜 Responsible use

This Actor only accesses public data via GitHub's official API. Use the data in compliance with GitHub's Terms of Service and applicable privacy/marketing laws (e.g. GDPR/CAN-SPAM) when contacting people.