Github Email Scraper avatar

Github Email Scraper

Pricing

from $2.99 / 1,000 commit emails

Go to Apify Store
Github Email Scraper

Github Email Scraper

Instantly extract contributor emails and detailed profiles from any public GitHub repository or organization to supercharge your developer outreach and recruiting.

Pricing

from $2.99 / 1,000 commit emails

Rating

0.0

(0)

Developer

w3crawler

w3crawler

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

4 days ago

Last modified

Categories

Share

GitHub Public Commit Email Scraper

Find email addresses that are visibly present in public GitHub commit metadata and aggregate them by address. For each public repository, the Actor inspects a bounded number of commit rows, deduplicates the addresses, keeps supporting repository and commit evidence, and can optionally enrich linked public GitHub profiles.

Public-only behavior

The source is public GitHub repository commit metadata, including the author/committer name and email that GitHub exposes on public commit responses. The Actor does not infer private addresses, scrape authenticated pages, access private repositories, bypass CAPTCHA or rate limits, or send write requests. GitHub noreply addresses are identified as such, but no claim is made that a public email is currently deliverable or belongs to a particular person beyond the source record.

The public repository commit history is a rendered GitHub surface with commit links, authors, timestamps, and messages. The Actor uses GitHub's documented public REST representation of those public commit rows because it provides the same source fields in a bounded, stable response. A caller-supplied token is optional for public API rate-limit headroom and is never written to the dataset or summary.

Input

{
"githubIds": ["apify/apify-cli"],
"maxCommitsPerRepo": 50,
"maxProfiles": 20,
"enrichProfiles": true,
"maxItems": 100,
"timeoutMs": 30000
}

githubIds accepts public users, organizations, or owner/repository values and is required by the input schema. A repository ID inspects that repository; a user or organization ID expands to at most maxRepos recently updated public repositories. maxCommitsPerRepo is capped at 1,000, maxProfiles at 100, and maxItems at 1,000. Profile enrichment is optional and bounded. Timeouts are 1–120 seconds. Unknown input keys are rejected. Proxy configuration is retained only for Store compatibility; this Actor uses direct public GitHub requests.

Dataset output

Each normal row contains a public email, source-derived name, optional GitHub login, numeric profile ID, public avatar/profile URL, repositories where the address appeared, repository URLs, the bounded commit_count, supporting commit SHAs, first/last observed commit timestamps, is_github_noreply, optional public profile fields, the public repository sourceUrl, and scrapedAt. These fields are source-backed and useful for public contributor analysis. Internal record IDs, success flags, source-website labels, transport labels, and request counters are not emitted in normal rows.

Operational failures are summarized in OUTPUT, including repositories, inspected commit rows, API requests, contributor count, failed requests, and failure details. The Actor does not create fake email rows for unavailable repositories.

Dataset example

{
"name": "Octocat",
"email": "octo@users.noreply.github.com",
"login": "octocat",
"repositories": ["octocat/Hello-World"],
"repository_urls": ["https://github.com/octocat/Hello-World"],
"commit_count": 3,
"commit_shas": ["abc123"],
"is_github_noreply": true,
"sourceUrl": "https://github.com/octocat/Hello-World",
"scrapedAt": "2026-08-24T00:00:00.000Z"
}

You can download the dataset in various formats such as JSON, HTML, CSV, or Excel.

Local run

npm ci
npm run check
npm test
apify validate-schema
apify run --purge --input-file input.json
npm run validate

Respect GitHub terms and applicable privacy laws. Keep the commit and repository bounds modest and use the data only for legitimate public-source purposes.