# GitHub Profile Scraper – User Data, Emails & Social Links (`devil_port369-owner/github-profile-scraper`) Actor

Scrape public GitHub user profiles without a token. Extract bio, company, location, followers, repos count, public email, and emails/social links from bio. Linear JSON for lead gen and talent research.

- **URL**: https://apify.com/devil\_port369-owner/github-profile-scraper.md
- **Developed by:** [DataFusionX](https://apify.com/devil_port369-owner) (community)
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $1.00 / 1,000 results

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

### What does GitHub Profile Scraper do?

**GitHub Profile Scraper extracts complete public profile data for any GitHub user or organization — including bio, company, location, follower counts, repo counts, and social links — using just a username or profile URL.** It is built for developers, recruiters, and growth teams who need clean, structured GitHub profile data without hand-scraping pages or hitting GitHub API rate limits. Unlike the official GitHub API, this Actor requires no personal access token, handles batches of usernames in one run, and normalizes messy input (raw usernames or full profile URLs) automatically. Choose it over manual API calls when you need speed, batch processing, and zero-auth setup.

### Why scrape GitHub profiles? (Business Use Cases)

- **Developer Recruiting & Sourcing** — Build candidate shortlists by pulling bios, company affiliations, and activity signals (public repos, followers) at scale for technical recruiting pipelines.
- **Competitive & Market Intelligence** — Track key engineers, maintainers, or founders at competitor companies to understand where technical talent and open-source investment is concentrated.
- **Academic & OSS Research** — Study contributor demographics, growth of developer communities, or influence patterns across open-source ecosystems.
- **Lead Generation for Dev Tools** — Identify high-follower or high-repo-count developers as outreach targets for developer-tool marketing and community programs.

### Key Features

- Accepts raw usernames *or* full GitHub profile URLs — no need to pre-clean input
- Batch processing of multiple profiles in a single run
- No GitHub authentication or personal access token required
- Structured JSON output ready for CSV, Excel, or database import
- Fast, low compute-unit cost per profile scraped
- Graceful handling of non-existent or deleted accounts (`exists: false`) instead of failing the run

### Input Parameters

| Parameter | Type | Required | Default | Description |
| --- | --- | --- | --- | --- |
| `usernames` | Array of strings | Yes | — | List of GitHub usernames or full profile URLs (e.g. `"octocat"` or `"https://github.com/torvalds"`) to scrape |

Valid input sample:

```json
{
  "usernames": [
    "octocat",
    "https://github.com/torvalds"
  ]
}
```

### Output Data Structure

Each item in the output dataset represents one scraped profile, including identity fields (`id`, `name`, `bio`), activity metrics (`public_repos`, `followers`, `following`), and metadata (`created_at`, `avatar_url`, `scraped_at`).

```json
[
  {
    "username": "octocat",
    "id": 583231,
    "name": "The Octocat",
    "company": "@github",
    "location": "San Francisco",
    "public_repos": 8,
    "followers": 24060,
    "following": 9,
    "created_at": "2011-01-25T18:44:36Z",
    "html_url": "https://github.com/octocat",
    "exists": true,
    "scraped_at": "2026-09-15T05:14:03.263925+00:00"
  }
]
```

### How to use GitHub Profile Scraper

1. Configure the `usernames` input parameter with the list of profiles you want.
2. Click "Start" or trigger a run via the Apify API, Python, or JavaScript SDK.
3. Preview the resulting dataset directly in the Apify Console.
4. Export results to JSON, CSV, or Excel, or push them onward via Zapier, Make, or Webhooks.

### Integrations & Export Options

GitHub Profile Scraper plugs directly into Apify's dataset export pipeline (JSON, CSV, Excel, XML) and integrates with n8n, Zapier, and Make for no-code automation. Results can also be piped into database pipelines (Postgres, BigQuery, Airtable) via Apify's built-in integrations or webhook triggers for real-time syncing.

### Custom Scrapers & Enterprise Automation Solutions

> Need a customized scraping solution, tailored workflow automation, or enterprise data extraction pipeline? Get custom development, maintenance, and setup tailored to your exact infrastructure requirements:
> 📬 **[Submit Your Custom Automation Requirements](https://mk1995.github.io/contact/)**

### Frequently Asked Questions (FAQ)

**1. Is scraping GitHub profiles legal and compliant?**
Scraping publicly available GitHub profile data is generally permissible, but you should always review GitHub's Terms of Service and applicable data protection laws (e.g. GDPR) before using scraped data commercially, especially for personal data like emails.

**2. How much does it cost to scrape GitHub using this Actor?**
Cost depends on Apify platform compute-unit usage, which scales with the number of profiles scraped per run — pricing is typically a fraction of a cent per profile at scale.

**3. Do I need proxies or coding skills to run this scraper?**
No coding is required — configure the input in the Apify Console UI and run it. No custom proxy setup is needed for this Actor.

**4. How does this compare to the official GitHub API?**
The official GitHub API requires authentication and enforces strict rate limits (60 requests/hour unauthenticated). This Actor removes that friction, batching multiple profile lookups without a token and returning normalized, ready-to-use JSON.

# Actor input Schema

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

GitHub usernames or profile URLs (e.g. octocat, https://github.com/octocat).

## Actor input object example

```json
{
  "usernames": [
    "octocat",
    "https://github.com/torvalds"
  ]
}
```

# Actor output Schema

## `results` (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 = {
    "usernames": [
        "octocat",
        "https://github.com/torvalds"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("devil_port369-owner/github-profile-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 = { "usernames": [
        "octocat",
        "https://github.com/torvalds",
    ] }

# Run the Actor and wait for it to finish
run = client.actor("devil_port369-owner/github-profile-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 '{
  "usernames": [
    "octocat",
    "https://github.com/torvalds"
  ]
}' |
apify call devil_port369-owner/github-profile-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,devil_port369-owner/github-profile-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/W7ZpzwQIuzJmV17ZT/builds/rSoXvjBNz8RsBKXkg/openapi.json