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
3 days ago
Last modified
Categories
Share
Extract verified developer, CTO, founder, and contributor emails, full names, company/organization affiliations, personal websites, X/Twitter handles, LinkedIn URLs, locations, and bios from any GitHub repository (owner/repo) or list of GitHub usernames — running in 256MB RAM with zero GitHub API tokens or proxies required.
Why Choose This GitHub Email Lead Scraper?
- Bypasses GitHub's 60-Req/Hour Unauthenticated API Rate Limit: Instead of relying solely on
api.github.com, our 3-tier engine inspectsgithub.comAtom commit feeds (commits.atom,{user}.atom), raw git commit.patchheaders (From: Name <email@company.com>andCo-authored-by:), and direct profile HTML parsing. - Uncovers Hidden Commit Emails: Even when developers hide their email on their public GitHub profile page, their git commit
.patchheaders frequently expose their real work or personal email address. - Automatic
@users.noreply.github.comFiltering: Automatically separates real deliverable emails (primaryEmail,emails) from GitHub noreply aliases while still extracting the contributor's full profile metadata. - External Website & Blog Email Crawler: Optionally follows the developer's linked personal blog or company website (
websiteUrl) to extract additional contact emails and social profiles.
Input Parameters
| Field | Type | Default | Description |
|---|---|---|---|
repositories | array | ["apify/crawlee"] | GitHub repositories (owner/repo or full URL) to extract developer leads from. |
usernames | array | [] | Specific GitHub usernames or profile URLs to enrich. |
maxLeadsPerRepo | integer | 15 | Maximum unique developer leads to extract per repository. |
crawlPersonalWebsites | boolean | true | Crawl linked developer blog/company website for additional emails. |
onlyWithVerifiedEmail | boolean | false | Only return leads with at least one verified deliverable email. |
Output Example
{"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}
Community & 24/7 Support
Join the Loujess Substrate engineering community for n8n templates, Claude MCP configs, and live signal feeds: https://discord.gg/YPwHmPMEQ