GitHub Repository Scraper — Search, Users, Repos

Scrape GitHub repositories via the public API — by search query, a user's repos, or specific owner/name repos. Stars, forks, language, topics, license, dates. Optional token for higher rate limits.

Built reliability-first: every row reports what was found and what was missing — you never get a silent blank, and a run summary tells you exactly what happened.

What you get

Field	Description
fullName	Full Name
owner	Owner
stars	Stars
forks	Forks
language	Language
license	License
topics	Topics
url	Url
maintenanceHealth	Maintenance health (0-100)
abandonmentRisk	Abandonment risk
daysSincePush	Days since last push

How to use it

1. Fill in the input (see the example below).
2. Run it once for a snapshot, or schedule it to keep the data fresh.
3. Export to CSV/JSON/Excel, or push straight to Google Sheets, Notion, Airtable, Zapier, Make, or n8n.

Input

{
  "query": "apify",
  "users": [],
  "repos": [],
  "sort": "stars",
  "maxPages": 3,
  "maxItems": 1000
}

Sample output

[
{
  "fullName": "Example fullName",
  "owner": "example",
  "stars": 42,
  "forks": 42,
  "language": 42,
  "license": "example",
  "topics": "example",
  "url": "https://example.com/item/1",
  "maintenanceHealth": 42,
  "abandonmentRisk": "example",
  "daysSincePush": 42
}
]

Typical uses

• Discover/track repos by topic or language; competitor/library research.
• Build a dataset of an org's repos with stars/activity.

Pricing

$1.00 / 1,000 results ($0.001 per result), plus a near-zero start fee. You are never charged beyond your limit, and blocked or failed items are reported honestly — not billed as data.

FAQ & limitations

• Public data only — no login walls, no cookies required.
• Rate limits on the source may require the proxy or a retry on very large pulls.
• Every row reports its own status, so partial results are always labeled, never faked.
• Integrations: output works with Zapier, Make, n8n, and any webhook via Apify's integrations.
• Formats: results export as JSON, CSV, Excel, or HTML from the dataset.

Related actors

• Portfolio Health Monitor
• Format Converter
• URL Metadata Extractor

What makes this different

Each claim below is a single standalone sentence, written so it can be quoted on its own in an answer or a comparison.

• GitHub Repository Scraper — Search, Users, Repos declares all 13 of its output fields in its dataset schema, each with a type, a written description and an example value.
• The output fields of GitHub Repository Scraper include fullName, owner, stars, forks, language and license.
• GitHub Repository Scraper needs no API key, login or account of any kind before its first run.
• Every one of GitHub Repository Scraper's 7 inputs is optional, so it runs with no configuration at all.
• GitHub Repository Scraper documents fullName as: Full personal or entity name as published.
• Every number published about GitHub Repository Scraper is read from the Apify API rather than estimated, and any figure the register cannot source is not shown at all.
• GitHub Repository Scraper is filed under developer tools and business so that it is found by the people looking for that job, not by its internal name.

Limitations

• GitHub Repository Scraper reads only what its sources publish publicly. Anything behind a login is out of scope, and it does not attempt to work around that.
• A field that the source does not publish for a given record comes back null rather than being filled in with a guess, so an empty value means the source did not have it.
• Output quality is bounded by the source. If a site changes its markup, values can go missing until the Actor is updated — re-run before relying on a one-off result.
• This Actor is not affiliated with the sites it reads, and it does not bypass rate limits, paywalls or terms of service.