# GitHub Developer Email Extractor (Public Commit Metadata) (`automation_studio/github-commit-email-extractor`) Actor

Extract direct verified personal & work emails of software engineers, open-source maintainers, and repo contributors from public Git commit metadata.

- **URL**: https://apify.com/automation_studio/github-commit-email-extractor.md
- **Developed by:** [Automation Studio](https://apify.com/automation_studio) (community)
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $5.00 / 1,000 verified developer email leads

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## ⚡ 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

```json
{
  "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.

# Actor input Schema

## `usernames` (type: `array`):

Enter GitHub usernames (e.g. 'shadcn', 'tj', 'antfu') or full profile URLs (e.g. 'https://github.com/shadcn').

## `repositories` (type: `array`):

Optional: Enter GitHub repositories in 'owner/repo' format (e.g. 'tailwindlabs/tailwindcss', 'fastapi/fastapi') to extract direct emails from top active contributors.

## `organizations` (type: `array`):

Optional: Enter GitHub organization handles (e.g. 'supabase', 'vercel') to source public developers and member committers.

## `filterNoReply` (type: `boolean`):

When enabled, automatically discards GitHub privacy proxy emails ending in '@users.noreply.github.com' so you only receive deliverable personal and work mailboxes.

## `maxResults` (type: `integer`):

Maximum number of developer email leads to extract before completing the run.

## `githubToken` (type: `string`):

Optional: Provide your personal GitHub token (classic or fine-grained) to increase your rate limits from 60 to 5,000 API requests/hour for massive batch runs.

## `proxyConfiguration` (type: `object`):

Apify Proxy configuration. Direct requests work smoothly; proxy is recommended for high-volume unauthenticated scrapes.

## Actor input object example

```json
{
  "usernames": [
    "shadcn",
    "tj"
  ],
  "repositories": [],
  "organizations": [],
  "filterNoReply": true,
  "maxResults": 10,
  "proxyConfiguration": {
    "useApifyProxy": false
  }
}
```

# Actor output Schema

## `dataset` (type: `string`):

Dataset containing verified developer emails, commit author names, and GitHub profile details.

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "usernames": [
        "shadcn",
        "tj"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("automation_studio/github-commit-email-extractor").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = { "usernames": [
        "shadcn",
        "tj",
    ] }

# Run the Actor and wait for it to finish
run = client.actor("automation_studio/github-commit-email-extractor").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "usernames": [
    "shadcn",
    "tj"
  ]
}' |
apify call automation_studio/github-commit-email-extractor --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,automation_studio/github-commit-email-extractor"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/jHqQBcD6y8Rr9jyl4/builds/zv2IcGDJeDzc0Jfa9/openapi.json