# GitHub Developer, Founder & Stargazer Email Lead Scraper (B2B) (`church_of_loujess/github-email-leads-scraper`) Actor

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.

- **URL**: https://apify.com/church_of_loujess/github-email-leads-scraper.md
- **Developed by:** [H H](https://apify.com/church_of_loujess) (community)
- **Categories:** Lead generation, Developer tools
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $15.00 / 1,000 enriched github developer & founder 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.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

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, Founder & Stargazer Email Lead Scraper (B2B)

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 inspects `github.com` Atom commit feeds (`commits.atom`, `{user}.atom`), raw git commit `.patch` headers (`From: Name <email@company.com>` and `Co-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 `.patch` headers frequently expose their real work or personal email address.
- **Automatic `@users.noreply.github.com` Filtering:** 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

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

# Actor input Schema

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

List of GitHub repositories to extract contributor and developer leads from (e.g. \['apify/crawlee', 'https://github.com/langchain-ai/langchain']).

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

Optional list of specific GitHub usernames or profile URLs to enrich (e.g. \['torvalds', 'https://github.com/karpathy']).

## `maxLeadsPerRepo` (type: `integer`):

Maximum number of unique developer/contributor leads to extract per repository.

## `crawlPersonalWebsites` (type: `boolean`):

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` (type: `boolean`):

When enabled, filters out leads that only have a @users.noreply.github.com address and no real personal/corporate email.

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

Optional proxy settings. Works out-of-the-box with direct connections via GitHub Atom feeds and .patch commit inspection.

## Actor input object example

```json
{
  "repositories": [
    "apify/crawlee"
  ],
  "usernames": [],
  "maxLeadsPerRepo": 10,
  "crawlPersonalWebsites": true,
  "onlyWithVerifiedEmail": false,
  "proxyConfiguration": {
    "useApifyProxy": false
  }
}
```

# Actor output Schema

## `overview` (type: `string`):

No description

# 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 = {
    "repositories": [
        "apify/crawlee"
    ],
    "usernames": [],
    "maxLeadsPerRepo": 10
};

// Run the Actor and wait for it to finish
const run = await client.actor("church_of_loujess/github-email-leads-scraper").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 = {
    "repositories": ["apify/crawlee"],
    "usernames": [],
    "maxLeadsPerRepo": 10,
}

# Run the Actor and wait for it to finish
run = client.actor("church_of_loujess/github-email-leads-scraper").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 '{
  "repositories": [
    "apify/crawlee"
  ],
  "usernames": [],
  "maxLeadsPerRepo": 10
}' |
apify call church_of_loujess/github-email-leads-scraper --silent --output-dataset

```

## MCP server setup

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

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/nB9hNNirAbbjlv3uu/builds/QhVVkoh9YwPMBY9bq/openapi.json