How to Use the GitHub Stargazers Export

Before you start

• Awareness of safe usage:
  • Spread your extractions across multiple launches during daytime hours.
  • GitHub only displays the most recent 4,800 stargazers of a repository. This Phantom cannot access older stargazers beyond that limit.

Step 1: Provide repository URLs

Tell the Phantom which repositories you want to extract stargazers from. You can provide inputs in any of these formats:

• A URL:
  • Paste a single GitHub repository URL directly in the setup field.
  • Paste the URL of a Google Sheet with your GitHub repository URLs (make sure it’s shared with “Anyone with the link”).
  • Or upload a CSV file with your GitHub repository URLs (make sure it’s publicly accessible, and note that CSV upload is only available on paid plans).

→ If you’re using a spreadsheet, the Phantom defaults to the first column (A). To use a different column, enter the column’s header name in the field “Column name containing GitHub repositories URLs.”

Step 2: Configure extraction settings

Fine-tune how many repositories to process and how results are handled:

1. Number of repositories to process per launch (optional):
   • Default = 10.
   • If left empty, the Phantom processes all provided repositories in one run.
   • Keep in mind: GitHub only shows the top 100 stargazers per repository.
2. Number of stargazers to scrape per repository (optional):
   • Default = empty, the Phantom processes as many as possible, up to GitHub’s 4,800 limit.
3. Remove duplicated profiles found from multiple projects (Optional):
   • Enabled by default.
   • Keep enabled if you’re extracting multiple repositories and want each stargazer to appear only once in your results.

Result file settings (dropdown in setup)

1. Name your results file (optional)

   • You can customize the file name.

     If you rename the file between launches, the Phantom will create a new results file and start processing inputs from scratch.

2. Fields to keep (optional)
   • Export only the fields you care about by listing them (comma-separated).
     Example: profileUrl, job, location.
   • This generates a second CSV file with just those fields.
   • Learn more in our guide: Customize how your Phantom results files are saved.

Step 3: Select launch frequency

Choose how often the Phantom should run:

1. Launch manually: Start the Phantom yourself whenever you need.
2. Launch once at a specific time: schedule a one-time run at a set date and time.
3. Launch repeatedly: schedule regular runs (e.g. once per day, several times during working hours).
4. Launch after another Phantom: chain automations together so this Phantom starts right after another finishes.
5. Advanced scheduling: customize the exact minutes, hours, days, or months when the Phantom should run.

→ For a complete walkthrough of scheduling options, see our guide to scheduling Phantoms automatically.

Step 4 (Optional): Advanced settings

Advanced settings are available if you want to fine-tune how your Phantom runs, but by default they’re already optimized for most use cases.

We recommend leaving them as they are unless a guide specifically instructs you to change something.

→ For a detailed overview of all advanced options (like execution limits, retries, email notifications, proxies, webhooks, and file management), see our Advanced settings guide.

Launch and results

When you’re ready:

1. Click Launch to start your Phantom.
2. Once it finishes, open the Results tab in the Phantom console.
3. Download your results as a CSV or JSON file.

→ To learn how to export your data to Google Sheets, integrate with other tools, or reuse it in more automations, check our Access and Export your Phantom Results guide.

Export and input limits on the Free plan
If you’re on the Free plan or Free trial, some features are limited:
- CSV exports include only the first 10 rows of results.
- CSV download links (for dynamic viewing in Google Sheets or integrations) are not available.
- JSON exports are not available.
- CSV upload as an input method is not supported.
To unlock all features, you’ll need to upgrade to a paid plan.

What you give (Input) and What you get (Output)

This section gives you a detailed breakdown of everything you need to provide to run this Phantom, and everything you’ll receive once it completes.

What you give (Input)

What you get (Output)

Tips and troubleshooting

Common pitfalls

• Using a private spreadsheet (make sure it’s set to “Anyone with the link”).
• Expecting more than 4,800 stargazers: GitHub does not expose older stargazers.
• Expecting contact or personal data: this Phantom only extracts contributor information visible on the repository page.
  → To enrich contributors with profile details or emails, use the GitHub Profile Scraper Phantom.

If you run into issues

• Check how to troubleshoot your phantom using Logs.
• Browse the Fix Issues & Troubleshoot Errors section for solutions to common problems.
• Review our Automation Rate Limits by Platform guide.
• Check our Best Practices for Social Media Automation guide.

Suggested automations

• GitHub Profile Scraper → Collect detailed information about each stargazer (bio, repos, followers, etc.).
• GitHub User Search Export → Build larger developer lists using search, then combine with stargazer data.
• GitHub Contributors Export → Compare stargazers with repo contributors for deeper insights.
• AI Advanced Enricher → Summarize stargazer profiles or generate outreach-ready messaging.