GitHub Developer, Founder & Stargazer Email Lead Scraper (B2B)
Pricing
from $15.00 / 1,000 enriched github developer & founder email leads
GitHub Developer, Founder & Stargazer Email Lead Scraper (B2B)
Extract verified developer, CTO, founder, and contributor emails, company names, websites, X/LinkedIn handles, and bios from any GitHub repository or username via commit .patch headers and Atom feeds. Zero API keys or proxies needed.
Pricing
from $15.00 / 1,000 enriched github developer & founder email leads
Rating
0.0
(0)
Developer
H H
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
7 days ago
Last modified
Features
Share
What can GitHub Developer & Founder Email Scraper do?
GitHub Developer & Founder Email Scraper extracts verified personal & corporate developer emails, full names, company/organization affiliations, locations, bios, personal websites, X/Twitter handles, and LinkedIn URLs from any public GitHub repository (owner/repo) or list of GitHub usernames — using git commit .patch headers, Atom feeds, and profile website crawling in 256 MB RAM with zero GitHub PAT tokens or proxies:
| 📦 What you can extract | ⚙️ Features & integrations |
|---|---|
|
📧 Commit-verified emails ( |
🔓 Zero GitHub API token bypasses GitHub's 60-req/hour unauthenticated REST rate limit via Atom + |
Developers, AI engineers, and technical founders ignore generic LinkedIn InMails — and GitHub hides profile emails from logged-out visitors. However, git itself embeds the author's real email inside raw commit .patch headers (https://github.com/owner/repo/commit/<sha>.patch). This Actor automates Atom feed discovery + .patch inspection + personal website crawling in one ethical public-data workflow.
What data can I extract with GitHub Developer & Founder Email Scraper?
Point the Actor at competitor open-source repositories, framework ecosystems, or specific GitHub handles to build high-precision DevTools, infrastructure, and AI-engineering lead lists:
-
Git
.patch+ website verified emails: real deliverable inboxes, never noreply noise. Extracts author and co-author emails from commit.patchheaders plus linked developer websites (crawlPersonalWebsites: true), automatically discarding*@users.noreply.github.comand[bot]addresses fromemails[]while settinghasVerifiedEmail: true/false. -
Firmographic & career profile attributes: know where each engineer works and lives. Captures
fullName,company(e.g.@apify,@vercel,Stripe),location(e.g.San Francisco, CA,Prague),bio, andfollowers. -
Cross-channel social & web identity: reach engineers via email, X, LinkedIn, or personal blog. Extracts
websiteUrl,twitterUsername, andlinkedinUrldirectly from GitHub profile sidebars and crawled personal sites. -
Technical contribution context: authentic icebreakers for DevRel & recruiting. Includes
sourceRepositoryandsampleCommitTitleso outreach can reference the exact open-source repo or technical problem the engineer actually ships code in.
Need more specialized workflows? Combine this Actor with these dedicated tools from our suite:
- 🚀 Hacker News & Product Hunt Founder Leads Scraper: capture technical founders launching Show HN & Product Hunt projects daily
- 💬 Reddit Scraper & B2B Buyer-Intent API: find developers asking for SDK/tool alternatives in
r/devops,r/LocalLLaMA&r/SaaS- 🌐 Website Email, Phone & Tech Stack Finder: enrich company domains discovered in developer
companyorwebsiteUrlfields- 🔌 Substack, B2B Churn & Lead MCP Server: combine developer launches, Substack authors & website contacts inside Claude or Cursor
How much will GitHub Developer & Founder Email Scraper cost?
GitHub Developer & Founder Email Scraper uses a transparent Pay-Per-Event (PPE) pricing model, where you pay a tiny $0.05 Actor Start event plus a per-item fee for each Enriched GitHub Developer & Founder Email Lead. On the Apify Free plan ($5.00 monthly free credit included), it costs $0.05 per item ($50.00 per 1,000 results) — letting you extract up to 99 results every month for free.
Paid Apify plans automatically unlock volume discounts up to 70% off ($0.025 on Starter/Bronze, $0.02 on Scale/Silver, and $0.015 on Business/Gold, Platinum & Diamond) with zero residential proxy surcharges:
| Apify Plan / Tier | Price per extracted dataset item | Price per 1,000 results | Batch Depth & Unmasking | Approx. Monthly Capacity |
|---|---|---|---|---|
Free (FREE Trial Preview) | $0.05 | $50.00 | 5 items/run trial (items 1-2 100% unmasked, items 3-5 preview-masked) | ~99 trial results |
Starter (BRONZE — $29/mo) | $0.025 | $25.00 | Unlimited batch runs & 100% unmasked | ~1,158 results |
Scale (SILVER — $199/mo) | $0.02 | $20.00 | Unlimited batch runs & 100% unmasked | ~9,947 results |
Business (GOLD — $999/mo) | $0.015 | $15.00 | Unlimited batch runs & 100% unmasked | ~66,596 results |
Enterprise (PLATINUM / DIAMOND) | $0.015 / $0.015 | $15.00 | Unlimited batch runs & 100% unmasked | Custom high-volume SLA |
Free Trial vs. Paid Plan Unlock: On the Apify Free tier, runs execute in 5-item Trial Preview mode (items
1and2are returned100%unmasked so you can verify live email/data quality firsthand; items3to5mask emails, phones, and deep RAG/financial blobs). Upgrading to Apify Starter ($29/mo) or higher immediately unlocks unlimited batch extraction (1,000+items/run),100%unmasked emails and payloads, and up to 70% lower per-item pricing ($0.025on Starter down to$0.015on Business). Check the pricing tab for full details.
How do I use GitHub Developer & Founder Email Scraper?
GitHub Developer & Founder Email Scraper was designed to be effortless to start with — even if you have never configured proxies, cookies, or web scrapers before. Here is how to extract data in under a minute:
- Create a free Apify account using your email (includes
$5.00in monthly free usage credit). - Open GitHub Developer & Founder Email Scraper in Apify Console.
- Configure your target inputs (
repositories,usernames,maxLeadsPerRepo) in the Input tab (use Bulk edit to paste lists at once). - Adjust your results limit or optional enrichment filters to match your workflow.
- Leave Proxy Configuration on its default zero-proxy setting (
useApifyProxy: false) for lowest cost. - Click Save & Start and watch structured records stream into your Dataset in real time.
- Open the Storage tab to inspect your results as a clean table or raw JSON.
- Download your dataset in JSON, CSV, Excel (
.xlsx), or XML, or connect it directly to Clay, n8n, Make, Zapier, Google Sheets, or MCP.
⬇️ Input
Provide repositories (owner/repo or full GitHub URLs), usernames (handles or profile URLs), or both in a single run.
Mode 1: Repository Contributor & Ecosystem Mining (repositories)
Extracts active contributors and commit authors from any public GitHub repo — ideal for DevTools PLG, competitor OSS ecosystems, and senior engineering recruiting.
| Input / Configuration | What it returns |
|---|---|
"apify/crawlee", "langchain-ai/langchain" | Up to maxLeadsPerRepo enriched contributor profiles + .patch emails |
Full URL ("https://github.com/modelcontextprotocol/servers") | Normalized automatically to owner/repo |
Input JSON example:
{"repositories": ["apify/crawlee","modelcontextprotocol/servers"],"maxLeadsPerRepo": 25,"crawlPersonalWebsites": true,"onlyWithVerifiedEmail": true}
Mode 2: Direct GitHub Handle Enrichment (usernames)
Already have a list of GitHub usernames from stargazers, issue openers, conference speakers, or Discord/HN bios? Enrich each handle's recent public .atom commits and personal website.
| Input / Configuration | What it returns |
|---|---|
"B4nan", "https://github.com/karpathy" | Inspects {username}.atom commits + profile + personal blog for emails & socials |
Input JSON example:
{"repositories": [],"usernames": ["B4nan","sindresorhus"],"crawlPersonalWebsites": true,"onlyWithVerifiedEmail": false}
Complete Input Parameter Reference
| Parameter | Type | Default | Required | Description |
|---|---|---|---|---|
repositories | array | ["apify/crawlee"] | No | List of GitHub repositories to extract contributor and developer leads from (e.g. ['apify/crawlee', 'https://github.com/langchain-ai/langchain']). |
usernames | array | [] | No | Optional list of specific GitHub usernames or profile URLs to enrich (e.g. ['torvalds', 'https://github.com/karpathy']). |
maxLeadsPerRepo | integer | 15 | No | Maximum number of unique developer/contributor leads to extract per repository. |
crawlPersonalWebsites | boolean | true | No | When enabled, if a developer lists a personal blog or company website on their GitHub profile, fetches the homepage to discover additional contact emails and social links. |
onlyWithVerifiedEmail | boolean | false | No | When enabled, filters out leads that only have a @users.noreply.github.com address and no real personal/corporate email. |
proxyConfiguration | object | {"useApifyProxy": false} | No | Optional proxy settings. Works out-of-the-box with direct connections via GitHub Atom feeds and .patch commit inspection. |
⬆️ Output and setup
All extracted records stream incrementally into your run's Dataset under the Storage tab in Apify Console. Preview results as a clean interactive table, download in JSON, JSONL, CSV, Excel (.xlsx), XML, or RSS, or consume items directly via the Apify REST API, Python/Node.js SDKs, or MCP.
📦 Enriched human GitHub contributor lead (hasVerifiedEmail: true)
{"username": "B4nan","fullName": "Martin Adámek","primaryEmail": "jan.buchar@apify.com","emails": ["jan.buchar@apify.com"],"hasVerifiedEmail": true,"company": "@apify","location": "Prague, Czech Republic","bio": "Full-stack developer, creator of MikroORM","websiteUrl": "https://mikro-orm.io","twitterUsername": "B4nan","linkedinUrl": null,"followers": 1420,"sourceRepository": "apify/crawlee","sampleCommitTitle": "fix: fetch robots.txt through the crawler's HTTP client","profileUrl": "https://github.com/B4nan","billable": true}
📦 Unverified bot / noreply contributor (hasVerifiedEmail: false — filtered when onlyWithVerifiedEmail: true)
{"username": "apify-deps","fullName": "\"apify-deps[bot]\"","primaryEmail": null,"emails": [],"hasVerifiedEmail": false,"company": null,"location": null,"bio": null,"websiteUrl": null,"twitterUsername": null,"linkedinUrl": null,"followers": 0,"sourceRepository": "apify/crawlee","sampleCommitTitle": "chore(deps): dependency sweep — lockfile freshening (#4326)","profileUrl": "https://github.com/apify-deps","billable": true}
Output Field Dictionary
| Output Field | Type | Description |
|---|---|---|
username / fullName / profileUrl | string | GitHub login handle, display name, and canonical profile URL. |
primaryEmail / emails | str / array | Top deliverable email and all non-noreply emails discovered. |
hasVerifiedEmail | boolean | true when at least one deliverable non-noreply email was extracted. |
company / location / bio | string | null | Employer/org tag, geographic location, and developer bio. |
websiteUrl | string | null | Developer's personal blog, portfolio, or startup URL. |
twitterUsername / linkedinUrl | string | null | Linked X/Twitter handle and LinkedIn profile URL. |
followers | integer | GitHub follower count. |
sourceRepository | string | null | owner/repo where the developer was discovered (or direct_username). |
sampleCommitTitle | string | null | Recent commit message title providing technical outreach context. |
billable | boolean | Dataset billing status indicator. |
Notes, tips, and exceptions
- Why some contributors have
primaryEmail: null: Automated bots (dependabot[bot],renovate[bot],apify-deps) and developers who enable strict GitHub commit-email privacy (@users.noreply.github.com) without listing a personal website will showhasVerifiedEmail: false. SetonlyWithVerifiedEmail: truewhenever you only want rows with real deliverable emails! - Zero GitHub token needed: Because Atom feeds (
/commits.atom),.patchdiffs, and public HTML pages do not consumeapi.github.com's 60-req/hr unauthenticated quota, you never need to risk your personal GitHub token. - Cross-repo deduplication: If the same engineer contributes to 3 repositories in
repositories[], they are enriched and emitted only once.
What can you do with data from GitHub Developer & Founder Email Scraper?
GitHub Developer & Founder Email Scraper powers high-ROI automation, lead generation, and AI agent pipelines. Here are four proven step-by-step recipes:
🛠️ DevTools & AI-infrastructure bottom-up PLG outreach
Reach engineers actively committing to adjacent open-source stacks (MCP servers, vector DBs, Playwright/Crawlee, Kubernetes, Rust).
Recipe:
-
List 5–10 ecosystem repos. Pass complementary repos in
repositorieswithmaxLeadsPerRepo: 30andonlyWithVerifiedEmail: true. -
Segment corporate vs. indie domains. Split corporate emails (
@company.com) from@gmail.com/ personal domains. -
Reference
sampleCommitTitle. Send peer-to-peer engineering notes inviting beta feedback rather than generic sales copy.
Push enriched leads into Clay, Apollo, Attio, or HubSpot.
🎯 Senior AI / Rust / Systems engineering recruiting
Skip résumé keyword spam — source engineers who ship real production open-source commits in your exact language and location.
Recipe:
-
Mine benchmark repositories. Scrape contributors to leading Rust, CUDA, TypeScript, or ML repos.
-
Filter by
location&followers. Filter exported CSV rows matching US/EU timezones or target cities. -
Reach out via
primaryEmail+twitterUsername+linkedinUrl. Reference their open-source work directly.
Export directly to Ashby, Greenhouse, Lever, or Gem.
🚀 Enrich GitHub issue openers asking for enterprise features
Users opening issues on competitor repos (SSO, RBAC, self-hosting, rate limits) are high-intent commercial buyers.
Recipe:
-
Collect issue author handles. Gather usernames from high-priority competitor GitHub issues.
-
Run Mode 2 (
usernames). Pass handles intousernameswithcrawlPersonalWebsites: trueto uncover theircompanyand workprimaryEmail.
Combine with Website Email & Tech Stack Finder on their company domain.
🎙️ DevRel & hackathon community seeding
Invite active open-source maintainers to hackathons, podcasts, or grant programs.
Recipe:
-
Target niche topic repos. Scrape maintainers across 20 newly trending repositories.
-
Personalize via
websiteUrl&bio. Send personal invites to maintainers withfollowers >= 100.
Schedule monthly to discover emerging OSS leaders early.
Want to get other B2B, Social, Financial, or MCP Agent data?
Chain this tool with our other 128 MB / 256 MB zero-proxy Apify Scrapers and Live Streamable-HTTP MCP Servers:
🔌 Using GitHub Developer & Founder Email Scraper with the Apify API, SDKs & MCP
Automate GitHub Developer & Founder Email Scraper programmatically from Python, Node.js/TypeScript, cURL, workflow builders (n8n, Make, Zapier, Clay, Pipedream), or Model Context Protocol (MCP) AI clients.
Python (apify-client)
from apify_client import ApifyClientclient = ApifyClient("<YOUR_APIFY_API_TOKEN>")run = client.actor("church_of_loujess/github-email-leads-scraper").call(run_input={"repositories": ["apify/crawlee","modelcontextprotocol/servers"],"maxLeadsPerRepo": 25,"crawlPersonalWebsites": True,"onlyWithVerifiedEmail": True})for item in client.dataset(run["defaultDatasetId"]).iterate_items():print(item)
Node.js / TypeScript (apify-client)
import { ApifyClient } from 'apify-client';const client = new ApifyClient({ token: '<YOUR_APIFY_API_TOKEN>' });const run = await client.actor('church_of_loujess/github-email-leads-scraper').call({"repositories": ["apify/crawlee","modelcontextprotocol/servers"],"maxLeadsPerRepo": 25,"crawlPersonalWebsites": true,"onlyWithVerifiedEmail": true});const { items } = await client.dataset(run.defaultDatasetId).listItems();console.log(`Extracted ${items.length} items:`, items);
One-Line Synchronous REST API (cURL — ideal for n8n, Make & Clay HTTP Columns)
curl -X POST "https://api.apify.com/v2/acts/church_of_loujess~github-email-leads-scraper/run-sync-get-dataset-items?token=<YOUR_APIFY_API_TOKEN>" \-H "Content-Type: application/json" \-d '{"repositories": ["apify/crawlee", "modelcontextprotocol/servers"], "maxLeadsPerRepo": 25, "crawlPersonalWebsites": true, "onlyWithVerifiedEmail": true}'
Claude Desktop, Cursor, Windsurf & OpenAI MCP Configuration
{"mcpServers": {"apify-github-email-leads-scraper": {"url": "https://mcp.apify.com/?actors=church_of_loujess/github-email-leads-scraper","headers": {"Authorization": "Bearer <YOUR_APIFY_API_TOKEN>"}}}}
❓ Frequently Asked Questions
How do I avoid getting bot accounts (dependabot, apify-deps) or empty email rows?
Set "onlyWithVerifiedEmail": true. Automated bots and noreply-only accounts have hasVerifiedEmail: false and are cleanly excluded before output!
Does this require a GitHub Personal Access Token (GITHUB_TOKEN)?
No. It uses public Atom commit feeds, raw .patch commit headers, and public profile HTML — zero GitHub tokens or logins needed.
How does .patch email discovery work?
Every public git commit on GitHub exposes its standard git email header at commit/<sha>.patch (From: Name <email@domain.com>). When a developer commits using their local git config user.email, that address is part of the public git history.
Does it filter out @users.noreply.github.com addresses?
Yes — GitHub noreply aliases cannot receive external mail, so they are automatically stripped from emails[] and primaryEmail.
Can I enrich specific GitHub usernames without specifying a repository?
Yes! Leave repositories: [] and pass handles in usernames: ["torvalds", "B4nan"]. The Actor inspects each user's public {username}.atom activity feed plus their profile and personal website.
What happens if crawlPersonalWebsites is true?
When a developer lists a personal blog or company URL (websiteUrl) on their GitHub profile, the Actor fetches that homepage to discover additional contact emails and LinkedIn/X links.
Is it legal to extract public data with GitHub Developer & Founder Email Scraper?
GitHub Developer & Founder Email Scraper only accesses publicly available web pages, feeds, and registries that require no private account login or authentication bypass. Keep in mind that extracted contact fields (such as public business emails, names, or usernames) can still qualify as personal data under frameworks like the GDPR or CCPA depending on jurisdiction. Always ensure you have a lawful basis (such as legitimate B2B interest) and consult Apify's guide on the legality of web scraping.
Can I integrate GitHub Developer & Founder Email Scraper with Clay, n8n, Make, Zapier, or Google Sheets?
Yes. Every run outputs clean, flat-friendly fields alongside nested detail objects and integrates natively with Clay, n8n, Make, Zapier, Slack, HubSpot, Airtable, Google Sheets, Airbyte, LangChain, and CrewAI via Apify Integrations. You can also attach webhooks to trigger downstream workflows automatically the instant a run succeeds.
Can I call GitHub Developer & Founder Email Scraper programmatically via the Apify API?
Yes. Use the official apify-client Python package or Node.js NPM package, or call the synchronous /run-sync-get-dataset-items REST endpoint directly. Full specifications are in the Apify API v2 reference.
GitHub Developer & Founder Email Scraper not working or need a custom feature?
We actively maintain and monitor all 26 Actors and MCP Servers in our portfolio. If you encounter an edge case, unexpected output, or want to request a new field, please open a ticket on the Actor's Issues tab with your Run ID so we can resolve it rapidly.