# GitHub Repos Scraper – Public Repositories by User or Org (`devil_port369-owner/github-repo-scraper`) Actor

Scrape public GitHub repositories for any user or organization without a token. Stars, forks, language, topics, license, homepage, and emails/social links from descriptions. Linear JSON rows.

- **URL**: https://apify.com/devil\_port369-owner/github-repo-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.20 / 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 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:

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

```json
[
  {
    "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](https://mk1995.github.io/contact/)**

### 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.

# Actor input Schema

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

User or org logins, or profile URLs (e.g. octocat, github, https://github.com/torvalds).

## `maxRepos` (type: `integer`):

Maximum repositories to return per user or org. 0 = all public pages.

## `includeForks` (type: `boolean`):

Include forked repositories in results.

## `sort` (type: `string`):

Sort order for listed repos.

## Actor input object example

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

# 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-repo-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-repo-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-repo-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-repo-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/XTxkNGqfegSi1RXe3/builds/4ocNTGOyQBXJlVlhB/openapi.json