⚡ GitHub Developer Email Extractor (Public Commit Metadata)

The Secret Weapon for Tech Recruiters, DevTool Founders, and Open-Source Sponsors.

Software engineers, open-source maintainers, and tech leads almost universally keep their direct email hidden on their public GitHub profile.

However, Git is a decentralized version control protocol. Every time an engineer pushes code to any public repository, their direct commit author email and full name are permanently embedded into public Git metadata.

This actor inspects unauthenticated public Git event streams, commit history, and raw patch headers to extract real developer personal (@gmail.com) and company work emails with 100% accuracy.

---

🚀 Key Features

• 🔓 Git Commit Metadata Extraction: Bypasses the hidden profile UI by inspecting public Git events and commit author records directly.
• 🚫 Smart Noreply Filtering: Automatically discards useless @users.noreply.github.com placeholder addresses so your cold outreach never bounces.
• 🏷️ Intelligent Email Classification: Automatically categorizes emails into PERSONAL, CORPORATE, ACADEMIC, or NOREPLY.
• 📦 Repository Contributor Sourcing: Pass any repository (e.g. tailwindlabs/tailwindcss, fastapi/fastapi, shadcn-ui/ui) to extract direct emails of active open-source contributors.
• 🏢 Organization Member Sourcing: Extract public developers across top tech companies (e.g. supabase, vercel, stripe).
• 🌐 Rich Profile Enrichment: Automatically captures GitHub bio, company, location, hiring availability (hireable), Twitter/X handle, and portfolio website.
• ⚡ Real-Time Streaming: Pushes records microsecond-by-microsecond as each developer lead is verified.
• 💎 Fair Pay-Per-Event Guarantee: Only pay for successfully extracted, non-noreply developer leads.

---

📋 Input Parameters

Parameter	Type	Default	Description
usernames	Array	["shadcn", "tj"]	List of target GitHub usernames or profile URLs.
repositories	Array	[]	Optional: List of GitHub repos (owner/repo) to extract active contributors from.
organizations	Array	[]	Optional: List of GitHub organizations to extract public members from.
filterNoReply	Boolean	true	When true, discards privacy proxy addresses (@users.noreply.github.com).
maxResults	Integer	10	Maximum number of verified developer leads to extract.
githubToken	String	null	Optional: Your personal GitHub token (PAT) to unlock 5,000 requests/hr for large batches.
proxyConfiguration	Object	Direct	Apify Proxy configuration for large batch jobs.

---

📊 Sample Output Record

{
  "username": "torvalds",
  "name": "Linus Torvalds",
  "email": "torvalds@linux-foundation.org",
  "emailType": "CORPORATE",
  "company": "Linux Foundation",
  "location": "Portland, OR",
  "hireable": false,
  "bio": "Creator of Linux and Git",
  "twitterUsername": "",
  "blog": "",
  "publicRepos": 7,
  "sourceRepo": "torvalds/linux",
  "latestCommitDate": "2026-10-05T14:36:06Z",
  "latestCommitMessage": "Merge tag 'procsysctl-6.12-rc2' of git://git.kernel.org/...",
  "profileUrl": "https://github.com/torvalds",
  "extractionSource": "REPO_AUTHOR_COMMIT"
}

---

🔒 Safety & Rate Limits

• Unauthenticated Requests: Works completely out-of-the-box without requiring any GitHub account or API key.
• Zero Scraping Bots: Uses official public Git commit event endpoints and raw patch headers.
• Higher Rate Limits: Pass an optional GitHub Personal Access Token (PAT) in githubToken to process up to 5,000 developers per hour.