GitHub Repo Info Scraper – Full Repository Details

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:

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

[
  {
    "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

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.