GitHub Issues Scraper

GitHub Issues Scraper

Scrape GitHub issues from any public repository, up to a million per run. Each issue comes with its title, body, state, labels, author, and timestamps. No API token required. Export to CSV, JSON, Excel, or XML.

GitHub's official API needs authentication, rate limits, and pagination code. This reads the public issues page directly, so you get a clean dataset of GitHub issues from any repository URL. Filter by state, label, or author, and export the results in one fixed schema.

Who uses it	What they scrape GitHub for
Open source maintainers	Which issues are most active or stale in their repository
Product managers	What users are requesting or complaining about in a competitor's repo
Data analysts	Trends in issue volume, labels, or authors over time
Researchers	A dataset of issue text for NLP or community health studies

What it does

This Actor collects GitHub issues from a repository URL and returns each issue as a flat row.

• 🔗 Repository URL input: paste any public GitHub issues page, like https://github.com/facebook/react/issues
• 📊 Flat row output: every issue becomes one row with title, body, state, labels, author, and timestamps
• 📦 Export formats: download as CSV, JSON, Excel, or XML
• ⚡ High volume: paid users can scrape up to 1,000,000 issues per run

Results export to CSV, JSON, Excel, or XML, or straight from the API.

What you can do with GitHub data

📈 Track issue trends.

A product manager scrapes a competitor's repository weekly to see which feature requests are gaining traction.

🧹 Clean up stale issues.

A maintainer exports all open issues, sorts by last update, and closes ones that have been inactive for a year.

📊 Analyze community health.

A researcher collects issue text and labels from several repos to measure response times and sentiment.

🔍 Find bug reports.

A developer scrapes issues with the 'bug' label to build a prioritized fix list.

Why choose this scraper

	What you get
No API token	Scrape public issues without registering an app or dealing with rate limits
One fixed schema	Every issue comes back with the same fields, ready for analysis
Export anywhere	CSV, JSON, Excel, or XML for your existing workflow

How it compares

No other Store actor targets GitHub the same way, so the honest comparison is with the alternatives teams actually weigh.

	GitHub Issues Scraper	Build it in-house	By hand
Setup	Run it now, zero config	Days of engineering	None, but hours per pull
When GitHub changes	Maintained for you	You fix it	You re-learn the page
Proxies, retries, anti-bot	Built in	Your problem	Browser only
Output	Fixed JSON schema, CSV/Excel export	Whatever you build	Copy-paste
Cost	Pay per result	Engineering time	Analyst hours

Configure the run

Drive the Actor with a single repository URL and set the maximum number of issues to return. The scraper reads the public issues page and returns each issue as a flat row. The Input tab lists every parameter.

A first run with the defaults:

{
 "repositoryUrl": "https://github.com/facebook/react/issues",
 "maxItems": 10
}

A larger pull:

{
 "repositoryUrl": "https://github.com/facebook/react/issues",
 "maxItems": 200
}

Pricing

Pay-per-result: $0.004 per result collected. You pay only for the results written to your dataset.

Results collected	Approximate cost
100 results	$0.40
1,000 results	$4.00
10,000 results	$40.00

New Apify accounts start with $5 in free credit.

Free users

Free-plan runs return up to 10 results as a preview. Upgrade your Apify plan to collect up to 1,000,000 results per run.

Run it

1. Create a free Apify account with $5 in credit.
2. Open the GitHub Issues Scraper.
3. Set your inputs and any filters, then click Start.
4. Export the results as CSV, Excel, JSON, or XML from the Dataset tab.

Run it programmatically through the Apify API (run-sync-get-dataset-items) or the ApifyClient for JavaScript and Python.

Use with AI agents (MCP)

Give an AI agent live access to GitHub through the Model Context Protocol. Add the Actor to Claude, Cursor, or any MCP client:

$claude mcp add --transport http apify "https://mcp.apify.com?tools=parseforge/github-issues-scraper"

Then prompt it in plain language to run the scraper and read back the results.

Troubleshooting

Why am I getting no results?

Check that the repository URL is correct and points to a public issues page, like https://github.com/facebook/react/issues. Also ensure the repository has at least one issue.

Why did the run stop at 10 items?

Free users are limited to 10 items as a preview. Upgrade to a paid plan to scrape more, up to 1,000,000 issues.

Why are some issues missing?

The scraper reads the public issues page, which may not include pull requests. If you need pull requests, use a different tool or the GitHub API.

Why is the run slow?

Scraping many issues takes time because the Actor respects GitHub's rate limits. Reduce maxItems or run during off-peak hours.

Can I scrape issues from a specific label only?

Not yet. The current input only accepts a repository URL. You can filter the exported dataset by label after the run.

FAQ

Question	Answer
Do I need a GitHub API token?	No. This Actor reads the public issues page directly, so no authentication is required.
Can I scrape private repositories?	No, only public repositories are supported. Private repos require authentication that this Actor does not handle.
What is the maximum number of issues I can scrape?	Free users are limited to 10 issues as a preview. Paid users can scrape up to 1,000,000 issues per run.
What data does each issue include?	Each issue row includes the title, body, state, labels, author, and timestamps. The exact fields are shown in the sample output.
Can I filter issues by label or author?	The current input only accepts a repository URL and a maximum item count. Filtering by label or author is not yet supported.
How do I export the data?	After the run finishes, you can download the dataset as CSV, JSON, Excel, or XML from the Apify platform.
Does this work with GitHub Enterprise?	No, it only works with public repositories on github.com.
Can I schedule regular scrapes?	Yes, you can set up a schedule in Apify to run this Actor daily, weekly, or at any interval.
What if the repository has more issues than my maxItems?	The Actor will stop after reaching the maxItems limit. If you need more, increase the limit up to 1,000,000 for paid users.
Is this an official GitHub tool?	No, this is a third-party scraper built on the Apify platform. It is not affiliated with GitHub, Inc.

Related actors

Browse the full ParseForge collection for more scrapers.

🆘 Need help? Email parseforge@protonmail.com with your run ID, your input, and what you expected.

⚠️ Disclaimer. This Actor is unofficial and is not affiliated with, endorsed by, or sponsored by GitHub, Inc. It collects only publicly available data. You are responsible for using the collected data in compliance with the source's terms of service and applicable data-protection laws, including GDPR, CCPA, and PIPL. Do not use it to collect personal data unlawfully.