GitHub trend research in 2026 is less about star screenshots and more about catching ranked repo moves early, then checking whether search or package adoption follows. GitHub's own Trending page is free. The GitHub REST API allows 5,000 authenticated requests per hour (60 unauthenticated) for custom scrapes of public metadata (GitHub Docs rate-limit page, accessed August 1, 2026). Trends MCP returns a live GitHub Trending Repos board on the free plan of 100 requests/month, and npm package octokit showed 7,804,248 recent download volume with +726.09% growth over 12 months (Trends MCP API, August 1 2026). The shortlist below matches tools to discovery, automation, and adoption checks.
What "GitHub trending" actually measures
GitHub Trending is a discovery board for repositories gaining attention over a short window. It is not a search-volume chart, and it is not a downloads chart. A repo can trend on stars and social shares while package installs stay flat, or the reverse can happen for libraries that grow quietly through dependency trees.
Search demand for the phrase "github trending" rose 320.0% over 12 months to a recent value of 42.0, and was still up 40.0% over 6 months before a 34.38% drop over 3 months (Trends MCP API, July 25 2026 snapshot). Broader "GitHub" search interest sat at a recent value of 50.0 with estimated recent_volume 6,340,000, up 138.1% over 12 months and 66.67% over 6 months, then down 50.0% over 30 days from a 100.0 peak baseline (Trends MCP API, July 18 2026 points). Those numbers describe interest in GitHub as a surface, not the quality of any single repo on today's board.
Live GitHub Trending Repos board for August 1 2026
A Trends MCP get_top_trends call with type GitHub Trending Repos returned 15 repositories at as_of_ts 2026-08-01T18:01:36Z. Rank 1 was microsoft/AI-For-Beginners. Rank 2 was paperswithbacktest/awesome-systematic-trading. Rank 3 was usekaneo/kaneo. Rank 4 was zhaoxuya520/reverse-skill. Rank 5 was microsoft/generative-ai-for-beginners. Later ranks included github/copilot-sdk, github/gh-stack, huggingface/speech-to-speech, iv-org/invidious, and bytedance/deer-flow.
That board is the discovery step. Adoption follow-ups need a second source. Search interest for "copilot sdk" sat at a recent value of 13.0 and fell 67.5% over 30 days and 86.46% over 6 months (Trends MCP API, July 25 2026 snapshot), which is a reminder that a trending repo name does not automatically mean rising search demand. The product page for the GitHub Trending Repos API documents the board call and the practical follow-up pattern.
Tool comparison for GitHub trend research
| Tool | Role | Cost signal (accessed Aug 1 2026) | Strength | Weakness |
|---|---|---|---|---|
| GitHub Trending (web) | Manual discovery | Free | Official ranks, language filters | No API contract for the board |
| GitHub REST API | Custom telemetry | Free within rate limits | Stars, forks, issues, search endpoints | Must build ranking logic and storage |
| libraries.io | Dependency / package discovery | Free open project | Cross-ecosystem package signals | Brand search demand is thin |
| Sourcegraph | Code search across repos | Check current pricing | Finds usage patterns inside code | Not a daily trending board |
| Trends MCP | Ranked board + growth | Free 100 req/mo; Starter $19/mo | Live GitHub Trending Repos JSON for agents | No native star-growth source |
GitHub's web Trending page remains the fastest human check. It fails as soon as a workflow needs scheduled JSON, alerts inside Slack, or an agent that can call tools. There is no official public endpoint that returns the same board Trends MCP exposes as type GitHub Trending Repos, which is why teams either scrape HTML (fragile) or use a normalized feed.
The GitHub REST API is the right layer when the research question is custom: watch star deltas for a watchlist, poll releases, or search repositories by topic. Authenticated personal access tokens get 5,000 requests per hour; unauthenticated clients get 60 per hour; GitHub App installations start at 5,000 and can scale higher on Enterprise Cloud (GitHub Docs, accessed August 1, 2026). Search interest for "github api" rose 357.14% over 12 months to a recent value of 32.0, with +52.38% over 6 months and -58.44% over 30 days (Trends MCP API, July 25 2026 snapshot). That YoY spike matches heavier automation interest even while the short window cooled.
libraries.io helps when the question shifts from "which repo is loud today" to "which packages are spreading through dependency graphs." Search interest for "libraries.io" had a recent value of 8.0 against a 12-month baseline of 0.0, then fell 42.86% over 6 months and 55.56% over 3 months (Trends MCP API, July 25 2026 snapshot). Treat those figures as a thin brand signal, not as proof of package adoption. For npm packages that match a trending repo name, Trends MCP get_growth on source npm is the cleaner adoption check.
Sourcegraph is a code-intelligence product, not a trending homepage. It earns a slot when researchers need to answer "who is importing this pattern" across many repositories. Public self-serve pricing should be verified on Sourcegraph's site at purchase time rather than quoted from secondary roundups. Search interest for "sourcegraph" rose 41.18% over 12 months to 24.0, then fell 36.84% over 6 months and 51.02% over 3 months (Trends MCP API, July 25 2026 snapshot).
Trends MCP fills the board-plus-signal gap for AI clients and scripts. Free is 100 requests/month; Starter is $19/mo for 1,000; Pro is $49/mo for 5,000; Business is $199/mo for 25,000 (Trends MCP pricing page, accessed August 1, 2026). One call pulls the live GitHub board. Follow-up calls on google search or npm measure whether attention is turning into broader demand. That pattern pairs well with AI trend research tools and MCP servers for trend research.
Demand and adoption figures behind the shortlist
| Signal | Metric | Value | Source label |
|---|---|---|---|
| github trending | 12M growth | +320.0% | Trends MCP API, July 25 2026 |
| github trending | recent value | 42.0 | Trends MCP API, July 25 2026 |
| github api | 12M growth | +357.14% | Trends MCP API, July 25 2026 |
| open source trends | 12M growth | +120.0% | Trends MCP API, July 25 2026 |
| open source trends | 3M growth | -80.0% | Trends MCP API, July 25 2026 |
| octokit (npm) | 12M growth | +726.09% | Trends MCP API, August 1 2026 |
| octokit (npm) | recent_volume | 7,804,248 | Trends MCP API, August 1 2026 |
| octokit (npm) | 12M baseline_volume | 940,848 | Trends MCP API, August 1 2026 |
| GitHub board | row count | 15 | Trends MCP API, August 1 2026 |
| GitHub REST API | authenticated hourly limit | 5,000 | GitHub Docs, Aug 1 2026 |
The octokit npm series is the clearest adoption signal in this set: download volume moved from 940,848 to 7,804,248 over the 12-month comparison, with +208.94% over 6 months and +19.12% over 3 months still positive (Trends MCP API, August 1 2026). That matters for trend research because many GitHub workflows depend on Octokit clients; rising installs support the claim that API-based GitHub automation is not a niche hobby. "Open source trends" as a phrase rose 120.0% over 12 months to 11.0, then collapsed 80.0% over 3 months, so the category phrase alone is a weak timing signal compared with concrete board rows.
Who should skip which tool
Skip custom GitHub API scrapers when a daily ranked list is enough and nobody will maintain star-delta storage. Skip Sourcegraph when the only question is "what is trending today," because code search answers a different job. Skip Trends MCP when the team needs private org analytics or Dependabot-style security graphs; those live inside GitHub's own product surface. Skip treating libraries.io brand search as a market-size proxy; the recent value of 8.0 is too thin for that use.
A second limit: trending boards change within a day. The August 1 18:01Z scan above is a point-in-time sample, and an earlier same-day scan can disagree on both order and length. Publish the as_of_ts with every citation, and do not invent filler repos when a response returns fewer rows than the requested limit.
Sources
- GitHub REST API rate limits (accessed August 1, 2026)
- Trends MCP pricing (accessed August 1, 2026)
- GitHub Trending (accessed August 1, 2026)
- Trends MCP API growth, npm, and top-trends pulls, July 18 to August 1 2026