# GitHub Repo Info Scraper – Full Repository Details (`devil_port369-owner/github-repo-info-scraper`) Actor

Scrape deep public details for any GitHub repository without a token. Stars, forks, topics, license, languages, homepage, and emails/social links from description. One linear JSON row per repo.

- **URL**: https://apify.com/devil\_port369-owner/github-repo-info-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 Repo Info Scraper do?

**GitHub Repo Info Scraper extracts complete metadata for any public GitHub repository — stars, forks, license, topics, language breakdown, and more — from a repo URL or `owner/repo` string.** It's built for engineering leaders, investors, and researchers who need structured repository intelligence at scale without manually checking each repo's page. Unlike the raw GitHub API, this Actor optionally enriches results with a full per-language byte breakdown and normalizes mixed input formats automatically.

### Why scrape GitHub repository info? (Business Use Cases)

- **Due Diligence & Tech Stack Analysis** — Evaluate a target company's or dependency's repository health (stars, activity, license, open issues) before investment or adoption decisions.
- **Market & Trend Intelligence** — Track star growth, fork counts, and language composition across repositories to spot emerging technology trends.
- **Vendor & Dependency Risk Assessment** — Check license type, archive/disabled status, and update recency to flag risky or abandoned dependencies before they hit production.
- **Academic Research on Software Ecosystems** — Analyze language distribution and repository characteristics across large samples of open-source projects.

### Key Features

- Accepts repository URLs or `owner/repo` shorthand, mixed freely in one run
- Optional `includeLanguages` flag for full per-language byte-count breakdown
- Returns license, topics, fork/star/watcher counts, and archive/fork status in one call
- Structured JSON output ready for CSV, Excel, or BI dashboard import
- Low compute-unit cost per repository, even with language breakdown enabled
- Distinguishes user-owned vs. organization-owned repositories via `owner_type`

### Input Parameters

| Parameter | Type | Required | Default | Description |
| --- | --- | --- | --- | --- |
| `repositories` | Array of strings | Yes | — | List of repository URLs or `owner/repo` strings to fetch metadata for |
| `includeLanguages` | Boolean | No | `false` | Whether to include a full per-language byte-count breakdown in the output |

Valid input sample:

```json
{
  "includeLanguages": true,
  "repositories": [
    "https://github.com/cli/cli",
    "torvalds/linux"
  ]
}
```

### Output Data Structure

Each output item represents one repository's full metadata profile, including ownership, activity metrics, licensing, and (optionally) a language breakdown.

```json
[
  {
    "owner": "cli",
    "owner_type": "Organization",
    "name": "cli",
    "full_name": "cli/cli",
    "description": "GitHub's official command line tool",
    "language": "Go",
    "languages": {
      "Go": 7808369,
      "Shell": 41794
    },
    "topics": ["cli", "git", "github-api-v4", "golang"],
    "license": "MIT",
    "stars": 46281,
    "forks": 9027,
    "open_issues": 1092,
    "html_url": "https://github.com/cli/cli",
    "scraped_at": "2026-09-15T05:12:18.405721+00:00"
  }
]
```

### How to use GitHub Repo Info Scraper

1. Configure `repositories` and optionally enable `includeLanguages`.
2. Click "Start" or trigger a run via the Apify API, Python, or JavaScript SDK.
3. Preview the repository metadata dataset in the Apify Console.
4. Export to JSON, CSV, or Excel, or push it into Zapier, Webhooks, or Google Drive.

### Integrations & Export Options

Exports natively to JSON, CSV, Excel, and XML, with direct support for n8n, Zapier, and Make automation pipelines. Repository metadata can also feed straight into database pipelines (Postgres, BigQuery, Airtable) or trigger webhook-based syncs for continuous monitoring dashboards.

### 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 repository info legal and compliant?**
Repository metadata is publicly available on GitHub, and scraping it is generally acceptable, but always review GitHub's Terms of Service before using the data at scale or commercially.

**2. How much does it cost to scrape GitHub repo info using this Actor?**
Cost is based on Apify compute units used per run, scaling with the number of repositories queried — enabling `includeLanguages` adds only marginal extra cost per repo.

**3. Do I need proxies or coding skills to run this scraper?**
No. The Actor is configured entirely through the Apify Console's input form, with no proxy setup or coding required.

**4. How does this compare to the official GitHub API?**
The GitHub REST API requires separate calls for repo metadata and language breakdowns, plus authentication for higher rate limits. This Actor combines both into a single normalized response across multiple repositories per run.

# Actor input Schema

## `repositories` (type: `array`):

Repo URLs or owner/name (e.g. https://github.com/cli/cli, torvalds/linux).

## `includeLanguages` (type: `boolean`):

Fetch /languages for byte counts per language (extra request per repo).

## Actor input object example

```json
{
  "repositories": [
    "https://github.com/cli/cli",
    "torvalds/linux"
  ],
  "includeLanguages": true
}
```

# 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 = {
    "repositories": [
        "https://github.com/cli/cli",
        "torvalds/linux"
    ]
};

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

# Run the Actor and wait for it to finish
run = client.actor("devil_port369-owner/github-repo-info-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 '{
  "repositories": [
    "https://github.com/cli/cli",
    "torvalds/linux"
  ]
}' |
apify call devil_port369-owner/github-repo-info-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-info-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/fAQvEb9hSwUlFTcgS/builds/9Zj8amwNAZbIuPTNI/openapi.json