GitHub Repository Metadata & README Extractor

Fetch stars, forks, topics, license, language breakdown and README text for GitHub repositories, by search query or a direct list of repository URLs. An optional personal token raises the request limit.

Open in Apify Store$0.99 / 1K on Free

Short answer

GitHub Repository Metadata & README Extractor is an Apify Store Actor for GitHub data that returns 19 published output fields, including htmlUrl, description, primaryLanguage, stars. It lists $0.99 per 1,000 results on the Free plan (pay per event), $0.49 on the Business plan. It takes 28 input settings, none required. It covers 5 of the 6 core GitHub fields this site tracks. Last updated Nov 11, 2026.

From the public Store listing and published build schema, synced 2026-11-12.
GitHub Developer toolsAutomationOpen source

What it returns

19 fields from the published dataset schema. Export as JSON, CSV or Excel, or read the dataset through the Apify API.

  • fullName
  • htmlUrl
  • description
  • primaryLanguage
  • stars
  • forks
  • watchers
  • subscribersCount
  • openIssues
  • visibility
  • topics
  • license
  • createdAt
  • updatedAt
  • pushedAt
  • latestRelease
  • contributorCount
  • commitActivityTotal
  • scrapedAt

Not in the schema among the core GitHub fields: repo. The field matrix shows which other tools return them.

How it differs from the other GitHub Actors

Among the 4 catalogue Actors for GitHub with a published schema, only this one returns watchers, subscribersCount, openIssues, visibility, createdAt, updatedAt, latestRelease, commitActivityTotal.

Pick another Actor if you need

Fields other GitHub catalogue Actors return that GitHub Repository Metadata & README Extractor does not
ActorFields it addsPrice / 1K
GitHub Weekly Trending Repos & Org Repo Finder trendingRank, repoUrl $0.99
GitHub Repository Language Breakdown Analyzer languagesBreakdown, repoUrl $0.99
GitHub Marketplace App & Action Listings by Category listingType, slug, installedCount, planType $0.99

Input

Input settings for GitHub Repository Metadata & README Extractor
SettingTypeRequiredDefaultWhat it does
mode string No search How to find repositories. 'search' runs a GitHub search query, 'direct' fetches an explicit list, 'owner' lists a user or organisation's repositories, and 'topic' lists repositories tagged with a topic.
searchQuery string No – GitHub search expression (mode=search). Supports qualifiers such as 'stars:>10000', 'language:python', 'topic:llm', 'user:apify', 'pushed:>2025-01-01', and 'in:name,description'. In owner/topic mode it is an optional keyword filter added to the owner or topic.
repositoryUrls array No [] Repositories to fetch (mode=direct). Accepts https://github.com/owner/repo, a trailing slash, .git, the git@github.com:owner/repo.git SSH form, or a plain owner/repo slug. Duplicates are removed.
owner string No – GitHub user or organisation whose repositories should be listed (mode=owner). Accepts 'apify' or 'https://github.com/apify'.
topic string No – Topic tag to browse (mode=topic), e.g. 'llm', 'machine-learning', or 'web-scraping'. A leading 'topic:' is accepted and stripped.
sortBy string No stars Sort key for search, owner, and topic results.
sortOrder string No desc Ascending or descending order for the selected sort key.
language string No – Only repositories whose primary language matches. Pick a common language here, or type any other language in 'Custom language'.
languageCustom string No – Any GitHub language name not listed above (e.g. 'Hare', 'Gleam'). Overrides the Language dropdown when non-empty.
license string No – Only repositories released under this license.
Show the other 18 settings
More input settings for GitHub Repository Metadata & README Extractor
SettingTypeRequiredDefaultWhat it does
searchIn string No – Where the free-text part of searchQuery must match (mode=search). Applies only when searchQuery contains free text.
minStars integer No 0 Only repositories with at least this many stars. 0 means no star filter.
minForks integer No 0 Only repositories with at least this many forks. 0 means no fork filter.
createdAfter string No – Only repositories created on or after this date (YYYY-MM-DD).
pushedAfter string No – Only repositories with a push on or after this date (YYYY-MM-DD). Useful for finding maintained projects.
includeForks boolean No false Include fork repositories in search, owner, and topic results. Direct mode always returns the repositories you list.
includeArchived boolean No true Keep archived repositories in the results. Turn this off to find actively maintained projects only.
maxResults integer No 30 Hard cap on repositories returned. GitHub's search API itself is capped at 1,000 results.
includeReadme boolean No true Fetch and include the decoded README text (capped at 500 KB).
includeTopics boolean No true Include the repository's topic tags.
includeLanguages boolean No true Include the byte count per programming language (one API request per repository).
includeRepoDetails boolean No false Fetch the repository detail endpoint in search, owner, and topic modes to add the real watcher count, network count, and organisation/parent fields (one extra API request per repository). Direct mode always fetches these.
includeReleases boolean No false Fetch the newest releases, including tag, dates, prerelease flag, and asset count (one request per repository).
releasesLimit integer No 10 How many releases to keep when 'Include releases' is on.
includeContributors boolean No false Fetch the ranked contributor list with contribution counts (one request per repository; GitHub caps this endpoint at 500 contributors).
contributorsLimit integer No 30 How many contributors to keep when 'Include contributors' is on.
includeActivity boolean No false Fetch 52 weeks of commit activity and the latest commit (up to two requests per repository; GitHub may need a moment to compute the statistics).
githubToken string No – Optional personal access token. It only raises the request limit from 60 to 5,000 requests per hour and is never required. A classic token with no scopes is enough for public data.

Example input

Built from the input form's published example values and defaults.

{
  "mode": "search",
  "searchQuery": "stars:>10000 language:python",
  "repositoryUrls": [
    "https://github.com/apify/crawlee"
  ],
  "sortBy": "stars",
  "sortOrder": "desc",
  "minStars": 0,
  "minForks": 0,
  "includeForks": false,
  "includeArchived": true,
  "maxResults": 30,
  "includeReadme": true,
  "includeTopics": true,
  "includeLanguages": true,
  "includeRepoDetails": false,
  "includeReleases": false,
  "releasesLimit": 10,
  "includeContributors": false,
  "contributorsLimit": 30,
  "includeActivity": false
}

Run it from code or an AI agent

The same run through the Apify API, with the example input. You need an Apify API token; the run is billed to your account at the Store price.

Python

from apify_client import ApifyClient

client = ApifyClient("<YOUR_APIFY_TOKEN>")
run_input = {
    "mode": "search",
    "searchQuery": "stars:>10000 language:python",
    "repositoryUrls": [
        "https://github.com/apify/crawlee"
    ],
    "sortBy": "stars",
    "sortOrder": "desc",
    "minStars": 0,
    "minForks": 0,
    "includeForks": False,
    "includeArchived": True,
    "maxResults": 30,
    "includeReadme": True,
    "includeTopics": True,
    "includeLanguages": True,
    "includeRepoDetails": False,
    "includeReleases": False,
    "releasesLimit": 10,
    "includeContributors": False,
    "contributorsLimit": 30,
    "includeActivity": False
}

run = client.actor("nimbryxo-studio/github-repository-metadata-and-readme-extractor").call(run_input=run_input)
if run is None:
    raise RuntimeError("The Actor run was not found.")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

pip install apify-client

JavaScript

import { ApifyClient } from "apify-client";

const client = new ApifyClient({ token: "<YOUR_APIFY_TOKEN>" });
const input = {
    "mode": "search",
    "searchQuery": "stars:>10000 language:python",
    "repositoryUrls": [
        "https://github.com/apify/crawlee"
    ],
    "sortBy": "stars",
    "sortOrder": "desc",
    "minStars": 0,
    "minForks": 0,
    "includeForks": false,
    "includeArchived": true,
    "maxResults": 30,
    "includeReadme": true,
    "includeTopics": true,
    "includeLanguages": true,
    "includeRepoDetails": false,
    "includeReleases": false,
    "releasesLimit": 10,
    "includeContributors": false,
    "contributorsLimit": 30,
    "includeActivity": false
};

const run = await client.actor("nimbryxo-studio/github-repository-metadata-and-readme-extractor").call(input);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(items);

npm install apify-client

cURL

curl -X POST "https://api.apify.com/v2/actors/nimbryxo-studio~github-repository-metadata-and-readme-extractor/run-sync-get-dataset-items"   -H "Authorization: Bearer $APIFY_TOKEN"   -H "Content-Type: application/json"   -d '{"mode":"search","searchQuery":"stars:>10000 language:python","repositoryUrls":["https://github.com/apify/crawlee"],"sortBy":"stars","sortOrder":"desc","minStars":0,"minForks":0,"includeForks":false,"includeArchived":true,"maxResults":30,"includeReadme":true,"includeTopics":true,"includeLanguages":true,"includeRepoDetails":false,"includeReleases":false,"releasesLimit":10,"includeContributors":false,"contributorsLimit":30,"includeActivity":false}'

Waits for the run and returns the dataset items (runs over 300 seconds return HTTP 408; start an async run instead).

MCP (AI agents)

{
  "mcpServers": {
    "apify": {
      "url": "https://mcp.apify.com?tools=nimbryxo-studio/github-repository-metadata-and-readme-extractor",
      "headers": {
        "Authorization": "Bearer <YOUR_APIFY_TOKEN>"
      }
    }
  }
}

Adds this Actor as a tool in an MCP client that takes a remote server URL (Cursor, VS Code, Claude Code) through Apify's hosted MCP server. OAuth sign-in also works without the header. Clients that only start local servers can wrap the URL with npx mcp-remote.

What a run costs

The result rate falls on higher Apify plans. Each figure is the published per-result rate times the number of results.

Cost of GitHub Repository Metadata & README Extractor results by Apify plan
Apify planPer 1,00010,000 results100,000 results
Free plan$0.99$9.90$99
Starter plan$0.82$8.20$82
Scale plan$0.66$6.60$66
Business plan$0.49$4.90$49
  • Every run also has a start event, charged per GB of memory (minimum one): $0.10 on Free, $0.03 on Business. At its default memory of 4 GB a run starts at $0.40 on Free. Fewer, larger runs keep this small.
  • The Free plan includes $5 of monthly usage (Apify pricing, checked 2026-11-11); at the Free rate that covers at most about 5,050 results, less start events and platform usage.
  • Worked example: 10,000 results in one run on the Free plan cost $10.30 ($9.90 for results + $0.40 start), plus Apify platform usage (compute), billed separately by Apify.
  • Pay per event. Platform usage (compute) is billed by Apify on top of the event prices. Compare other tools in the cost estimator.

Where it fits among GitHub routes

It ranks 1 of 4 catalogue Actors for GitHub on the published formula (fields, price, reliability, freshness). Its line is highlighted on the map.

Route diagram for GitHub dataGitHub Repository Metadata & README Extractor: stops at 9 of the 10 fields shown; GitHub Weekly Trending Repos & Org Repo Finder: stops at 6 of the 10 fields shown; GitHub Repository Language Breakdown Analyzer: stops at 7 of the 10 fields shown; GitHub Marketplace App & Action Listings by Category: stops at 2 of the 10 fields shown; Other Store tools (6): stops at 9 of the 10 fields shown; GitHub REST API: public, field coverage not compared.GitHublanguagedescriptionupdated atrepostarsurlfullNameforkstopicspushedAt1234+API

Stops are fields. A ring means the field is in that route's published output schema; no ring means the line passes without it. Bold labels are the core fields for this website, the rest are fields that differ between routes. A white capsule means every data line stops there. The red line is the official API; its field coverage is not compared. A crossed red line means there is no open official API.

Official route: GitHub REST API

Public API. The GitHub REST API exposes repositories, issues, releases, users, organisations and more. A token raises rate limits.

No per-call fee for standard REST API use.

Official documentation

Other Store tools for GitHub

Reference only, from their public listings.

Other Store tools for GitHub
ToolFieldsPrice / 1K
GitHub Repositories Search Scraper42$0.23
GitHub Repository & Trending Scraper8$0.50
GitHub Repository Scraper25$1.99
GitHub Repository Search & Scraper8$2.00
GitHub Repository Scraper–$2.00

What people use it for

  • research repositories
  • review project metadata and documentation

Other catalogue Actors for GitHub

GitHub Weekly Trending Repos & Org Repo Finder

Find GitHub repositories gaining stars this week, run keyword searches across all public repos, or list an organization's public repos with stars,…

4/6 core fields 9 output fields $0.99 per 1K

GitHub Repository Language Breakdown Analyzer

Pull repositories for a GitHub organization, a keyword search, or a single repo, with per-repo programming-language percentage breakdown, stars,…

3/6 core fields 9 output fields $0.99 per 1K

GitHub Marketplace App & Action Listings by Category

Search GitHub Marketplace apps and Actions by keyword, browse an entire category, or fetch listings by slug. Returns pricing plans, categories,…

2/6 core fields 9 output fields $0.99 per 1K

Google Fonts Library Metadata Extractor

Look up Google Fonts families by name, browse a category, or export the full library with weights, variable-font axes, language subsets,…

20 output fields $0.99 per 1K

Google Image Search Results & Metadata Scraper

Run a Google Images search and get back full-resolution image URLs with dimensions, thumbnails, source page titles, and the web page each image…

29 output fields $0.99 per 1K

Spotify Podcast Show & Episode Metadata Extractor

Search Spotify podcast shows and episodes, fetch a show's full episode list, resolve a show or episode by link, and browse categories by market -…

10 output fields $0.99 per 1K

Bilibili Video Search, Ranking & Metadata Scraper

Search Bilibili videos by keyword, look up specific videos by URL or ID, or pull the popular feed and partition ranking charts, with view, like…

6 output fields $0.99 per 1K

Medium Article Discovery & Metadata Extractor

Find Medium articles by tag, author, publication, keyword search or direct URL, returning title, author, tags, preview text, reading time, publish…

8 output fields $0.99 per 1K

Snapchat AR Lens Metadata & Related Spotlight Finder

Get trending Snapchat AR lenses, full lens details (creator, previews, related lenses, Spotlight videos using it) by URL or UUID, or lens search…

$0.99 per 1K

Questions people ask

How much does GitHub Repository Metadata & README Extractor cost?

The published result rate depends on your Apify plan: $0.99 per 1,000 on Free, $0.82 per 1,000 on Starter, $0.66 per 1,000 on Scale, $0.49 per 1,000 on Business. So 10,000 results cost about $9.90 on the Free plan and $4.90 on Business, plus a start fee of $0.10 per run per GB of memory on Free. Platform usage is billed separately.

What data does GitHub Repository Metadata & README Extractor return?

Its published output schema lists 19 fields: fullName, htmlUrl, description, primaryLanguage, stars, forks, watchers, subscribersCount, openIssues, visibility, topics, license, and 7 more. A listed field is not guaranteed to be filled in every row.

What input does GitHub Repository Metadata & README Extractor need?

No input is strictly required; the defaults run as is. Common settings: mode, searchQuery, repositoryUrls, owner, topic, sortBy.

What are the alternatives to GitHub Repository Metadata & README Extractor for GitHub?

4 catalogue Actors cover GitHub. Close alternatives: GitHub Weekly Trending Repos & Org Repo Finder; GitHub Repository Language Breakdown Analyzer; GitHub Marketplace App & Action Listings by Category. The GitHub page compares all of them field by field.

How do I run GitHub Repository Metadata & README Extractor from Python or the API?

Use the Apify API client: in Python, ApifyClient(token).actor("nimbryxo-studio/github-repository-metadata-and-readme-extractor").call(run_input=...), then read the run's default dataset (run.default_dataset_id); in JavaScript the same call is client.actor("nimbryxo-studio/github-repository-metadata-and-readme-extractor").call(input). Without a client, POST the input JSON to https://api.apify.com/v2/actors/nimbryxo-studio~github-repository-metadata-and-readme-extractor/run-sync-get-dataset-items with your API token. Ready-to-paste code with the example input is on this page.

Sources

Actor updated 2026-11-11 Data synced 2026-11-12
Cite this page

Scraper Finder. "GitHub Repository Metadata & README Extractor." https://scraperfinder.com/catalogue/github-repository-metadata-and-readme-extractor/ (data checked 2026-11-12).

Run GitHub Repository Metadata & README Extractor

$0.99 per 1,000 results. Paste the example input above, set your GitHub query, then export the dataset. Still choosing? Compare every GitHub route.

Open in Apify Store