GitHub Trending vs Google Trends live ranks

A GitHub Trending versus Google Trends comparison on Trends MCP is two get_top_trends calls: type GitHub and type Google Trends. From the August 27, 2026 pull, both boards stamped 2026-08-27T00:01:30 UTC. GitHub returned 16 owner/name rows at offset 0, then count 0 at offset 16. Google Trends returned 50 rows at offsets 0, 50, 100, and 150, filling ranks 1 through 200, then count 0 at offset 200. GitHub rank 1 was tt-a1i/archify. Google Trends rank 1 was dolly parton. Zero exact strings overlapped. google search for omarchy sat at 42.0 on 2026-08-22. Free tier access is 100 requests per month.

GitHub closed at 16 while Google Trends filled 200

From the Trends MCP scan of August 27, 2026, GitHub and Google Trends both stamped 2026-08-27T00:01:30 UTC, GitHub closed at 16 owner/name rows, and Google Trends filled 200, so a default limit 25 join misses every Google query after 25 and never sees that GitHub stopped early.

GitHub ranks 11 through 16 were anthropics/claude-plugins-community, ConardLi/garden-skills, browser-use/browser-use, K-Dense-AI/scientific-agent-skills, marin-community/marin, and VoltAgent/awesome-agent-skills. Google Trends ranks 11 through 20 included nvidia stock at 13, xrp price at 15, and google docs at 29. ChatGPT sat at App Store Top Free rank 1, Google Play rank 11, and Wikipedia Trending rank 22 on the same stamp, and still missed GitHub 16 and Google Trends 200. Wikipedia rank 1 matched Google Trends rank 1 as Dolly Parton.

How to pull both boards in one account

Two get_top_trends calls against the same Trends MCP key return GitHub and Google Trends as separate ranked lists, and REST mode get_top_trends bills each type and each page as its own request, so confirming GitHub at offset 16 plus paginating Google Trends through offset 200 is six requests before any get_growth follow-up.

{"mode": "get_top_trends", "type": "GitHub", "limit": 50, "offset": 0}
{"mode": "get_top_trends", "type": "Google Trends", "limit": 50, "offset": 0}

MCP clients send the same fields on get_top_trends. Passing type GitHub Trending Repos on this stamp still returned "type": "GitHub" with the same 16 rows, so treat GitHub as the canonical label and GitHub Trending Repos as an alias. The GitHub Trending Repos API page still describes a 12-row scan from August 1, 2026. This pull closed at 16. The Google Trends Trending Now API page documents the 200-row fill. Offset and limit behavior for both feeds is on get_top_trends pagination.

There is no github source on get_growth. Star history is not in this payload. Follow-ups use google search or npm on a related keyword, each billed as its own request.

Which GitHub repos match Google queries

Exact string matching on GitHub 16 versus Google Trends 200 returned zero shared titles, and repo tokens such as claude, omarchy, browser-use, obsidian, and github itself also missed the 200, so a production join needs an alias table rather than lowercase equality on owner/name.

Two Anthropic plugin repos sat on GitHub at ranks 3 and 11. Neither claude nor anthropic appeared in Google Trends 200. google docs at Google rank 29 had no GitHub counterpart. Token collisions such as meta versus a missing Meta repo are not matches. Do not treat a GitHub owner/name as a Google Trends query without an explicit alias.

Search and npm follow-ups diverge from GitHub rank

get_growth on google search and npm turns a live GitHub rank into a dated 0-100 index, and those indexes on this stamp did not move with GitHub rank: omarchy held GitHub 7 at google search 42.0 after a 200.0% 7-day rise, while browser-use at GitHub 13 sat at 11.0 after a 45.0% 7-day drop.

Shared google search recent_date 2026-08-22 unless noted:

npm package browser-use used recent_date 2026-08-29, a weekly point ahead of the August 27 board stamp. Quote that series date. There is no github growth source, so star counts are not in this table. omarchy search interest rose while the string stayed off Google Trends 200. Board heat is not search demand. npm follow-ups for other owner/name strings need the exact package name on npmjs.com; a repo name that is not a package returns no_data. See npm trends for the package-name contract.

GitHub rank_change empties after a 3d window

sort rank_change on GitHub lists only repos that sit on the current 16-row board and also sat on the chosen baseline, and on this August 27, 2026 stamp the 1d window returned count 3, the 3d window returned count 2, and the 7d, 14d, and 30d windows returned count 0 with a complete-turnover note.

The 1d list also included DietrichGebert/ponytail at rank 10, prev_rank 14, rank_change 4, and basecamp/omarchy at rank 7, prev_rank 9, rank_change 2. The 3d second row was anthropics/claude-plugins-community at rank 11, prev_rank 15, rank_change 4. A 7d lookback on a 16-row daily board can empty even when 1d still has climbers. Read the count field and the note. Do not assume a longer window lists more movers.

Limits of a GitHub versus Google Trends join

GitHub rows are owner/name strings, Google Trends rows are search queries, and those shapes do not share a key, so exact-string joins miss even when google search for a repo token is elevated, and rank_change cannot invent a prev_rank for a repo that was absent from the baseline snapshot.

limit 50 on GitHub still returned 16. Offset 16 returned count 0. Google Trends needed four pages of 50 to close at 200. Each page is a request. GitHub 1d rank_change used baseline 2026-08-26T02:01:36 UTC, the same 02:01 cluster as Google Trends, Wikipedia Trending, and Google Play on this stamp. New GitHub entries with no prev_rank never appear as climbers. There is no github source on get_growth. npm recent_date can land on a future week-ending date; the browser-use point was 2026-08-29. The free plan is 100 requests per month. Starter is $19 for 1,000, Pro is $49 for 5,000, and Business is $199 for 25,000.