# GitHub Developer, Contributor & Stargazer B2B Lead Scraper (`tungnguyen84/github-developer-contributor-lead-scraper`) Actor

Extract developer profiles, public emails, personal websites/blogs, X/Twitter handles, LinkedIn links, company names, locations, bio, and follower counts from GitHub repositories, contributors, and user profile URLs.

- **URL**: https://apify.com/tungnguyen84/github-developer-contributor-lead-scraper.md
- **Developed by:** [Tung Nguyen](https://apify.com/tungnguyen84) (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

$2.00 / 1,000 scraped github developer profiles

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, Contributor & Stargazer B2B Lead Scraper

Extract verified **Developer Profiles**, **Public Emails**, **Personal Websites & Blogs**, **X (Twitter) & LinkedIn Handles**, **Company Names**, **Locations**, **Bios**, and **Follower Counts** from any list of **GitHub Repositories** or **GitHub User/Organization URLs**.

### Built for Technical Recruiting, DevTools GTM & Open-Source B2B Outreach

Finding qualified software engineers, open-source maintainers, and DevTools decision-makers on LinkedIn is expensive and noisy. With this Actor, you can feed any GitHub repository (e.g., `https://github.com/apify/crawlee`) or list of developer profiles and automatically extract enriched B2B contact leads.

#### Key Features

- **Repository + Contributor Discovery**: Pass repository URLs or direct user profile URLs — the Actor automatically extracts repository metadata and crawls linked contributor/owner profiles.
- **Email & Social Enrichment**: Captures public profile emails, README/bio contact emails, personal blog URLs, X/Twitter profiles, and LinkedIn links while filtering out `noreply.github.com` placeholders.
- **Zero GitHub API Token Required**: Uses fast HTML & structured DOM parsing via `@crawlee/cheerio` so you never hit GitHub's strict 60 req/hr unauthenticated API block.

***

### Input Parameters

| Field | Type | Default | Description |
| :--- | :--- | :--- | :--- |
| `targetUrls` | `array` | Required | List of GitHub repository URLs or user profile URLs. |
| `maxProfiles` | `integer` | `30` | Maximum number of pages/profiles to extract per run. |

#### Example Input JSON

```json
{
  "targetUrls": [
    { "url": "https://github.com/tungnguyen84" },
    { "url": "https://github.com/apify/crawlee" }
  ],
  "maxProfiles": 30
}
```

***

### Output Dataset Sample

```json
{
  "recordType": "developer",
  "username": "tungnguyen84",
  "fullName": "Tung Nguyen",
  "profileUrl": "https://github.com/tungnguyen84",
  "repositoryUrl": null,
  "bio": "Full-Stack Automation Engineer, Web Scraping Architect & Open-Source Contributor",
  "company": null,
  "location": "Vietnam",
  "website": "https://rapidapi.com/user/tungnguyen84",
  "twitter": null,
  "linkedin": null,
  "emails": ["it.tungnguyen@gmail.com"],
  "followers": "15",
  "publicRepos": "42",
  "scrapedAt": "2026-11-01T09:40:00.000Z"
}
```

# Actor input Schema

## `targetUrls` (type: `array`):

List of GitHub repository URLs (e.g. https://github.com/apify/crawlee) or developer profile URLs (e.g. https://github.com/tungnguyen84) to extract contributor leads, emails, websites, X/Twitter, company, and location from.

## `maxProfiles` (type: `integer`):

Maximum number of GitHub developer profiles to enrich per run.

## Actor input object example

```json
{
  "targetUrls": [
    {
      "url": "https://github.com/tungnguyen84"
    },
    {
      "url": "https://github.com/apify/crawlee"
    }
  ],
  "maxProfiles": 30
}
```

# Actor output Schema

## `developers` (type: `string`):

Dataset containing GitHub developer and repository lead records.

# 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 = {
    "targetUrls": [
        {
            "url": "https://github.com/tungnguyen84"
        },
        {
            "url": "https://github.com/apify/crawlee"
        }
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("tungnguyen84/github-developer-contributor-lead-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 = { "targetUrls": [
        { "url": "https://github.com/tungnguyen84" },
        { "url": "https://github.com/apify/crawlee" },
    ] }

# Run the Actor and wait for it to finish
run = client.actor("tungnguyen84/github-developer-contributor-lead-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 '{
  "targetUrls": [
    {
      "url": "https://github.com/tungnguyen84"
    },
    {
      "url": "https://github.com/apify/crawlee"
    }
  ]
}' |
apify call tungnguyen84/github-developer-contributor-lead-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,tungnguyen84/github-developer-contributor-lead-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/cQ8k796mlL9QFFgZM/builds/4MK1xWuCglrwEdATT/openapi.json