GitHub Contributors Scraper – Repo Contributor Lists

What does GitHub Contributors Scraper do?

GitHub Contributors Scraper extracts the full contributor list for any public GitHub repository — including usernames, commit contribution counts, and profile links — from a repo URL or owner/repo string. It's built for open-source maintainers, engineering managers, and researchers who need to analyze who is really driving a codebase forward. Unlike scrolling through GitHub's paginated contributors tab, this Actor returns clean, structured data for one or many repositories in a single run, with no API token or rate-limit juggling required.

Why scrape GitHub contributors? (Business Use Cases)

• Open-Source Health Analysis — Assess how concentrated or distributed a project's contributions are, a key signal for dependency risk assessment before adopting a library.
• Engineering Talent Sourcing — Identify top contributors to influential repositories as strong recruiting leads for specialized roles (e.g. compilers, kernels, CLIs).
• Competitive Intelligence — Track which engineers are actively shipping code on a competitor's or partner's open-source projects.
• Academic Research on OSS Collaboration — Study contribution patterns, bus-factor risk, and maintainer turnover across large codebases like the Linux kernel.

Key Features

• Accepts repository URLs or owner/repo shorthand, mixed in the same run
• Configurable maxResults cap per repository, or unlimited (0) for full contributor lists
• Returns contribution counts alongside contributor profile metadata
• Structured JSON output ready for CSV, Excel, or BI tool import
• Efficient compute-unit usage even on large repositories with thousands of contributors
• Flags site-admin (GitHub staff) contributors via site_admin

Input Parameters

Parameter	Type	Required	Default	Description
repositories	Array of strings	Yes	—	List of repository URLs or owner/repo strings to scrape contributors from
maxResults	Integer	No	0	Maximum number of contributors to return per repository; 0 means no limit

Valid input sample:

{
  "repositories": [
    "https://github.com/cli/cli",
    "torvalds/linux"
  ],
  "maxResults": 0
}

Output Data Structure

Each output item represents one contributor to one repository, including the repo they contributed to, their GitHub identity, and their total contribution count.

[
  {
    "repo_full_name": "cli/cli",
    "repo_owner": "cli",
    "repo_name": "cli",
    "username": "mislav",
    "id": 887,
    "type": "User",
    "contributions": 2061,
    "html_url": "https://github.com/mislav",
    "site_admin": false,
    "scraped_at": "2026-09-15T05:13:20.716580+00:00"
  }
]

How to use GitHub Contributors Scraper

1. Configure repositories (and optionally maxResults) in the input.
2. Click "Start" or trigger a run via the Apify API, Python, or JavaScript SDK.
3. Preview the contributor dataset in the Apify Console.
4. Export to JSON, CSV, or Excel, or forward it through Zapier, Webhooks, or Google Drive.

Integrations & Export Options

Results export natively to JSON, CSV, Excel, and XML, and connect to no-code automation tools like n8n, Zapier, and Make. The Actor also supports direct database pipeline integrations (Postgres, BigQuery, Airtable) and webhook-triggered syncs for continuous contributor monitoring.

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

Frequently Asked Questions (FAQ)

1. Is scraping GitHub contributor data legal and compliant? Contributor data (username, contribution counts) is publicly displayed on GitHub and generally fine to collect, but always check GitHub's Terms of Service and relevant data protection regulations before commercial use.

2. How much does it cost to scrape GitHub contributors using this Actor? Cost scales with the number of repositories and contributors fetched, billed via Apify compute units — typically inexpensive even for repositories with thousands of contributors.

3. Do I need proxies or coding skills to run this scraper? No. The Actor runs from a simple JSON input in the Apify Console — no proxy configuration or coding required.

4. How does this compare to the official GitHub API? The GitHub REST API's contributors endpoint is paginated and rate-limited per token. This Actor automates pagination and batching across multiple repositories in one run, returning a single consolidated dataset.