GitHub Email Scraper - Find Emails from Commits
Pricing
from $2.00 / 1,000 email founds
GitHub Email Scraper - Find Emails from Commits
Extract contributor emails from GitHub commit history. Scan repos, users or orgs and get author emails, names and commit counts. No token required.
Pricing
from $2.00 / 1,000 email founds
Rating
0.0
(0)
Developer
Long Li
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
3 hours ago
Last modified
Categories
Share
GitHub Email Scraper Lite — Find Contributor Emails from Commit History
Give it a GitHub repository, user or organization and get back every human contributor email hidden in the commit history — deduplicated, with author names, linked GitHub accounts, commit counts and last-commit dates. The classic lead-gen move for developer tools, recruiting and outreach.
Works with the public GitHub API — no token required for small scans (add a personal access token for 5,000 requests/hour when scanning orgs at scale).
What you get
One dataset row per unique email:
| Field | Description |
|---|---|
email | Commit author email. |
name | Author name attached to the commits. |
githubUser | Linked GitHub login, when the commit author has an account match. |
repo | Repository where the email first appeared. |
commitCount | How many commits in the scanned window used it. |
lastCommitAt | Newest commit date with this email. |
isNoreply | True for GitHub-masked @users.noreply.github.com addresses. |
Noise is filtered for you: @users.noreply.github.com masks (excluded by default, toggle includeNoreply), GitHub web-flow bot committers, and obvious machine senders (dev.bot@, ci@, actions@...).
Input
| Field | Description |
|---|---|
| GitHub URLs | github.com/owner/repo to scan one repo, or github.com/owner to scan an account's recently pushed repos. |
| Max commits per repo | How deep to walk history (default 300). |
| Max repos per user/org | Account mode: how many active repos to scan (default 10; forks and archived repos skipped). |
| Include noreply | Keep GitHub-masked addresses. |
| GitHub token (optional) | Raises the rate limit from 60 to 5,000 req/h. |
| Max concurrent repos | Default 3, kept low to respect rate limits. |
How to find GitHub emails (the honest way)
Every git commit stores the author's email in public history — git log shows it locally, and the GitHub REST API exposes the same data for any public repo. GitHub's own "Keep my email address private" setting replaces it with an id+username@users.noreply.github.com mask; those addresses can't receive mail, so this actor flags and excludes them instead of selling you dead rows.
FAQ
Do I need a token? For a few repos up to a few hundred commits: no. For organization-wide scans: yes — a free personal access token (no scopes needed for public data) lifts the limit to 5,000 requests/hour. If the quota runs out mid-run, the actor degrades gracefully and reports partial results.
Why is an email I expected missing? The author has email privacy enabled (only their noreply mask commits), the commits come from a bot identity, or the email first appears deeper in history than your Max commits window — raise the limit.
Private repos? No. Public data only; a token with private scope still won't be used to read private commits.
Legal/ethical? Commit emails are published by their authors as part of open-source contribution metadata. Use for outreach responsibly — this is public data, but people still read what you send.
Related actors
- Contact Info Scraper Lite — emails, phones and social links from any website
- Cloudflare Bypasser Lite — fetch HTML from Cloudflare-protected pages
- Bluesky Scraper Lite · Mastodon Scraper Lite · Rumble Scraper Lite
Pricing
Pay-per-event: charged per unique email found (email-found event), plus platform usage. Failed scans cost nothing. While the actor is on the free plan, runs cost platform usage only.
