GitHub Scraper | Repos, Issues, PRs, Users & Topics avatar

GitHub Scraper | Repos, Issues, PRs, Users & Topics

Pricing

from $2.20 / 1,000 results

Go to Apify Store
GitHub Scraper | Repos, Issues, PRs, Users & Topics

GitHub Scraper | Repos, Issues, PRs, Users & Topics

Scrape GitHub.com repositories, issues, pull requests, discussions, users, topics, and organization repos. GitHub search + repo pages without a personal access token. Export Excel/CSV/JSON as a GitHub API alternative.

Pricing

from $2.20 / 1,000 results

Rating

0.0

(0)

Developer

kane liu

kane liu

Maintained by Community

Actor stats

0

Bookmarked

1

Total users

0

Monthly active users

a day ago

Last modified

Share

GitHub scraper for public GitHub.com pages — search and export repositories, issues, pull requests, discussions, users, topics, and organization repos without a personal access token. A practical GitHub API alternative when you need guest-visible metadata in CSV, Excel, or JSON, not source blobs or issue/PR bodies.

This Actor is built for no-code operators first: pick a search type, enter a query (or an org / topic slug), set maxResults, click Start, and download the Dataset. Developers can call the same Actor from the Apify API, Make, n8n, Zapier, LangChain, or a scheduled task.

Thin Apify Actor + Cloud Run worker. Guest HTML only. The worker owns residential egress. You do not send a GitHub PAT, cookies, or proxyUrl.


What does the GitHub Scraper do?

The GitHub Scraper collects public GitHub search and listing data that a logged-out visitor can already see in the browser. It is not a wrapper around the official GitHub REST/GraphQL API and it does not ask you for a token.

Give it a query and a searchType, or a topic slug / organization login. The Actor:

  1. Validates the input (query, searchType, owner/repo/org when required)
  2. Calls a managed worker that fetches github.com guest HTML
  3. Parses opened surfaces into normalized Dataset rows (identity, URL, language, stars, issue number, …)
  4. Dedupes and caps output with maxResults / maxPages
  5. Writes INPUT_ECHO, RUN_SUMMARY, and (on failure) ERROR_SUMMARY to the key-value store

Opened surfaces (what actually works)

Mode (searchType)What you scrapeRequired input
repositoriesGitHub repository searchquery
issuesIssue search results (title, number, URL — not the body)query
pullrequestsPull request search results (not PR detail / diff)query
discussionsDiscussion search results (not the thread body)query
usersUser / org search cards (login + profile URL)query
topicTopic page repo list (/topics/{slug})query = topic slug
orgReposOrganization repositories (/orgs/{org}/repositories)org (real org login)
repoPublic repo code page metadata (not file blobs)owner + repo
issueSingle issue listing-detail page (metadata, not body HTML)owner + repo + issueNumber from a live search href

Optional search qualifiers: language, sort, order. Optional detailUrls for live github.com repo / issue / org-repos / topic URLs.

Honest limits (read this before you buy a competitor)

This Actor stays on guest HTML. That is the point — and the constraint.

  • No GitHub PAT / no login. Opened guest surfaces work without a token. If a page is a sign-in wall, you get no rows — we do not store cookies or mint sessions.
  • No issue / PR / discussion bodies. Rows keep identity + URL + list metadata. body / bodyHTML are not written.
  • No source download. We do not fetch Git blobs, tarballs, or file contents. searchType=repo is the public repo page, not a zip of the tree.
  • Guest code search is a sign-in wall. searchType=code is wired in the schema but 未验证 — GitHub asks guests to sign in. Do not expect code-search rows.
  • Repo Issues LIST is unavailable. /owner/repo/issues as a list page is 未验证. Use issue search (searchType=issues) or a live issue URL (searchType=issue).
  • Search pagination hard-cap: 100 pages. Do not try to exhaust result_count. Set maxPages low and page with a tighter query.
  • Not opened: github.co.jp, GitHub Enterprise, Explore, Dashboard, Login, PR detail, org people.

Other Store Actors (for example deep GitHub scrapers that take a PAT and call REST/GraphQL, or issue-only REST scrapers) can pull bodies, files, or private-adjacent fields if you give them a token. This one does not. Use it when you want tokenless public search + topics + org repos, exported as tables.


What GitHub data can I extract?

Typical default-dataset fields (exact keys vary by mode):

FieldExample / notes
idGitHub node / numeric id when present
fullName / nameowner/repo or display name
ownerLogin / loginOwner or user login (login expected on users)
urlhttps://github.com/... link
kind / typerepository, issue, user, …
languagePrimary language on repo rows
stargazerCountStars when the card exposes them
numberIssue / PR number
status / stateList state when present

You get structured rows you can join, filter, and schedule — not a dump of issue markdown and not a clone of the repo.

You do not get: file contents, commit diffs, issue/PR/discussion bodies, emails from private profiles, or anything behind GitHub login.


Why scrape GitHub?

GitHub is the default index of public software, issues, and developer identity. Scraping public GitHub repositories, issues, pull requests, and users is useful when the official API is the wrong tool: rate limits, token ops, or you only need guest-visible cards in a spreadsheet.

Common jobs:

  • Repo discovery — find repositories by keyword, language, or topic (kubernetes, topic=rag, language:Go) and export stars + URLs
  • Issue / PR monitoring — track public issue and pull-request search hits for a library, CVE string, or product name without paging the API
  • Topic landscapes — pull live /owner/repo links from a GitHub topic page
  • Org inventories — list public repositories under a real organization (huggingface, supabase, deno)
  • User / org lookup — collect login + profile URLs from user search
  • Automation — feed CRM, recruiting, competitive intel, or an AI agent via CSV / JSON / the Apify Dataset API

Why not just use the GitHub API? The official API is the right choice when you already have a PAT, need bodies or files, or must query private repos you own. This Actor is a GitHub API alternative for guest HTML: no token to rotate, no GraphQL query to maintain, export-ready tables, and pay-per-result pricing.

Why not a PAT-based “deep” scraper? Those tools (multi-mode REST/GraphQL Actors, issue REST scrapers) are stronger when you want bodies, comments, or authenticated code search. They also mean storing a token and accepting API quotas. This Actor is the opposite trade: public, tokenless, list/search metadata only.


Pricing

Pay per event. You pay for Actor start + each result written to the default dataset. Platform compute / memory for this Actor is paid by the developer (User pays platform usage costs = No).

EventPrice
Actor Start (apify-actor-start)$0.005 per start (per GB of memory, minimum one event)
result (apify-default-dataset-item)$3.00 / 1,000 on FREE & BRONZE ($0.003 each)

Volume examples (FREE / BRONZE, one start at 1024 MB)

ResultsEvent charges (approx.)
100$0.005 + $0.30 = $0.305
1,000$0.005 + $3.00 = $3.005
10,000$0.005 + $30.00 = $30.005

Store volume tiers (per result)

Tier$/1,000per result
FREE$3.00$0.003
BRONZE$3.00$0.003
SILVER$2.60$0.0026
GOLD$2.20$0.0022
PLATINUM$2.00$0.002
DIAMOND$1.60$0.0016

Default memory is 1024 MB. Actor Start is charged per GB (minimum one event). Keep maxResults at 2–15 while you test a query.

Empty / failed runs that write zero default-dataset rows are not billed as results (you still pay Actor Start).


More Actors like this

Use a specialized Actor when one exists for your site — structured fields, better coverage, usually lower cost. Use GitHub Scraper for public GitHub search, topics, and organization repos. Use the general tools below when you need email/phone checks or a generic protected-page scrape.

General tools

Developer / Open source

Prefer a dedicated site scraper?

If your target has a specialized Actor below, use that first — usually cheaper and more structured than a generic URL scrape.

Jobs & Freelance

E-commerce

Real Estate

Travel & Stays

Social & Content

Ads Intelligence

Local & Maps

→ See the full catalog in Related Actors below, or browse apify.com/lentic_clockss.


How to scrape GitHub repositories

No code required.

  1. Open GitHub Scraper in Apify Console (Actor lentic_clockss/github-scraper).
  2. Set Search type — start with repositories (or users / topic / pullrequests / discussions / issues).
  3. Enter a Search query (for example language:python stars:>1000, or a topic slug like supabase when type is topic).
  4. For organization repos, set searchType to orgRepos and org to a real org login (not a user; vite is not an org).
  5. Set maxResults to 5–15 for a first run and maxPages to 1.
  6. Click Start. When the run finishes, open the Dataset tab.
  7. Download CSV, Excel, or JSON.

That is enough for most spreadsheet and no-code workflows. Developers can skip the UI and POST the same JSON to the Apify Runs API.

Example: scrape GitHub repositories

{
"query": "language:rust stars:>2000",
"searchType": "repositories",
"maxResults": 15,
"maxPages": 1
}

Example: scrape GitHub users

{
"query": "deno",
"searchType": "users",
"maxResults": 10,
"maxPages": 1
}

Example: scrape a GitHub topic

{
"query": "supabase",
"searchType": "topic",
"maxResults": 15
}

Example: organization repositories

{
"searchType": "orgRepos",
"org": "huggingface",
"repoType": "public",
"maxResults": 20
}

Connect to your tools

Use this Actor from your existing stack:

PlatformHow to connect
Make.comSearch "Apify" → "Run Actor" → Actor ID: lentic_clockss/github-scraper
n8nAdd Apify node → "Run Actor" → same Actor ID
ZapierApify integration → "Run Actor"
LangChainApifyActorsTool("lentic_clockss/github-scraper")
Python / Node.jsApify SDK or direct HTTPS call

API call example

curl "https://api.apify.com/v2/acts/lentic_clockss~github-scraper/runs" \
-X POST \
-H "Authorization: Bearer YOUR_APIFY_TOKEN" \
-H "Content-Type: application/json" \
-d '{"query":"langchain","searchType":"repositories","maxResults":10,"maxPages":1}'

Read results from the Dataset API:

GET https://api.apify.com/v2/datasets/{datasetId}/items?format=json

You can also schedule the Actor (daily topic watch, weekly org inventory) from Console.


FAQ

Do I need a GitHub personal access token? No. Opened guest surfaces — repository / issue / PR / discussion / user search, topic pages, org repos, and public repo/issue pages — run without a PAT. Do not paste a token into input.

Is this a GitHub API alternative? For public search and listing metadata, yes: you export CSV / Excel / JSON without managing API tokens or GraphQL. It is not a replacement when you need issue bodies, file contents, authenticated code search, or private repositories.

Can I scrape GitHub issues and pull requests? Yes — search results (searchType=issues or pullrequests) and a single issue LDP (searchType=issue + a live issueNumber). You get titles, numbers, URLs, and list metadata. You do not get issue/PR bodies. Repo Issues LIST and PR detail pages are not opened.

Can I download repository source code? No. This Actor does not clone repos or fetch blobs. Use git clone or the official API for source.

Why is code search empty? GitHub guest code search is a sign-in wall. searchType=code is not a supported opened mode. Use repository search, a topic page, or org repos instead.

Why did org repos fail / Unicorn? org must be a real organization login. Some popular names are users, not orgs (for example neovim is a user; vite is not an org). Use huggingface, supabase, kubernetes, or deno as a sanity check.

How many GitHub search pages can I paginate? maxPages is hard-capped at 100. GitHub search does not let guests walk the entire result set. Narrow query (language, stars, qualifier) instead of raising pages.

Is it legal to scrape GitHub? You are responsible for how you use the data. This Actor only collects public guest-visible page data, does not log in, and does not store issue/PR bodies. Follow GitHub Terms, robots rules, and your own compliance review. Unofficial — not affiliated with GitHub.

How is this different from other GitHub scrapers on Apify Store? Deep / PAT scrapers offer more modes (REST + GraphQL, issue bodies, code). Issue-only scrapers focus on the Issues API. Repo-only scrapers stop at repository cards. This Actor is tokenless guest HTML covering search + topics + org repos, with PPE at $3.00 / 1,000 results and developer-paid platform usage.

Do I need to bring proxies? No. Do not send proxyUrl. The worker provides egress (WORKER_PROVIDES_PROXY=1).

What if a run returns 0 rows? The query may be too tight, the mode may be a sign-in wall (code), or org may not be an organization. Retry with a broader query, an opened searchType, and a known org. CONNECT 562 is a transient worker/network miss — retry once.

Can I use it from Make, n8n, Zapier, or LangChain? Yes. Actor ID lentic_clockss/github-scraper. See Connect to your tools.


Input reference

FieldTypeDescription
querystringGitHub search q, or topic slug when searchType=topic
searchTypestringrepositories, issues, pullrequests, discussions, users, topic, orgRepos, repo, issue (opened). Others in the schema are 未验证 (code, issuesList, explore, dashboard, login, pull, orgPeople, githubJapan)
owner / repostringRequired for repo and issue
issueNumberintegerRequired for issue. Use a live search href; do not invent ids
orgstringRequired for orgRepos. Must be a real organization
repoTypestringOptional org filter: public, source, fork, archived, template (worker uses q=)
languagestringOptional language: qualifier / l=
sort / orderstringOptional search sort (stars, comments, followers) and order (desc)
maxResultsintegerCap emitted rows (schema 1–200)
maxPagesintegerSearch pages, hard cap 100
detailUrlsarrayOptional github.com repo / issue / org-repos / topic URLs. Issues LIST and PR detail URLs are rejected
workerBaseUrlstringOptional HTTPS override. Production source of truth is Actor env

Do not send proxyUrl, cookies, or a GitHub token.

Full output schema is on the Dataset tab. Key-value store: INPUT_ECHO, RUN_SUMMARY, ERROR_SUMMARY.


All 78 Actors from [lentic_clockss]. Click a name to open the Store detail page.

Jobs & Freelance

Real Estate

E-commerce

Travel & Stays

Social & Content

Ads Intelligence

Local & Maps

General Tools

→ Browse the full profile: apify.com/lentic_clockss