GitHub Repos Scraper – Public Repositories by User or Org

What does GitHub Repo Scraper do?

GitHub Repo Scraper extracts the full list of public repositories owned by any GitHub user, including stars, forks, license, and activity metadata, sorted and filtered to your needs. It's built for recruiters, analysts, and developer-tool teams who need a complete, structured inventory of a user's open-source work without manually paging through their GitHub profile. Unlike the raw GitHub API, this Actor lets you exclude forks, cap results per user, and sort output by recency in a single configurable run.

Why scrape GitHub user repositories? (Business Use Cases)

• Technical Due Diligence — Assess a developer's or founder's real body of open-source work — project scope, popularity, and maintenance activity — during hiring or investment evaluation.
• Talent Sourcing & Portfolio Review — Quickly review a candidate's repository history, star counts, and languages used as a proxy for technical depth.
• Competitive Product Research — Track which repositories a competitor's engineers are actively building or maintaining outside their main product.
• Open-Source Ecosystem Mapping — Study how prolific individual maintainers are and how their project portfolios evolve over time.

Key Features

• Accepts usernames or full profile URLs, mixed freely in the same run
• includeForks toggle to exclude forked repositories and focus on original work
• Configurable maxRepos cap per user, or unlimited (0) for the full list
• Sortable output (e.g. updated) to prioritize the most recently active repositories
• Structured JSON output ready for CSV, Excel, or dashboard import
• Efficient compute-unit usage even for prolific users with many repositories

Input Parameters

Parameter	Type	Required	Default	Description
usernames	Array of strings	Yes	—	List of GitHub usernames or profile URLs to fetch repositories for
includeForks	Boolean	No	true	Whether forked repositories should be included in the results
maxRepos	Integer	No	0	Maximum number of repositories to return per user; 0 means no limit
sort	String	No	"updated"	Sort order for returned repositories (e.g. updated, created, pushed, full_name)

Valid input sample:

{
  "includeForks": false,
  "usernames": [
    "octocat",
    "https://github.com/torvalds"
  ],
  "maxRepos": 0,
  "sort": "updated"
}

Output Data Structure

Each output item represents one repository owned by a scraped user, including ownership, popularity metrics, licensing, and status flags.

[
  {
    "owner": "torvalds",
    "owner_type": "User",
    "name": "linux",
    "full_name": "torvalds/linux",
    "description": "Linux kernel source tree",
    "language": "C",
    "license": "NOASSERTION",
    "stars": 249064,
    "forks": 64547,
    "open_issues": 3,
    "is_fork": false,
    "html_url": "https://github.com/torvalds/linux",
    "scraped_at": "2026-09-15T05:13:44.773285+00:00"
  }
]

How to use GitHub Repo Scraper

1. Configure usernames and optionally includeForks, maxRepos, and sort.
2. Click "Start" or trigger a run via the Apify API, Python, or JavaScript SDK.
3. Preview the resulting repository dataset in the Apify Console.
4. Export to JSON, CSV, or Excel, or forward it via Zapier, Webhooks, or Google Drive.

Integrations & Export Options

Results export natively to JSON, CSV, Excel, and XML, and integrate directly with n8n, Zapier, and Make for no-code automation. The dataset can also sync into database pipelines (Postgres, BigQuery, Airtable) or trigger webhook-based workflows whenever a run finishes.

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 user repositories legal and compliant? Repository listings are public GitHub data, and scraping them is generally permissible, but always review GitHub's Terms of Service and any applicable regulations before commercial use.

2. How much does it cost to scrape GitHub repos using this Actor? Cost scales with the number of users and repositories fetched, billed in Apify compute units — typically low-cost even for users with large repository portfolios.

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

4. How does this compare to the official GitHub API? The GitHub REST API paginates a user's repositories and requires authentication for higher rate limits. This Actor automates pagination, fork filtering, and sorting across multiple users in a single run.