Guide
Last updated: 2026-06-02
GitHub Trending is one of the most-watched signals in open source — a quick read on which projects the developer community is paying attention to right now. But the page is easy to misread: it is not a list of the biggest or most popular repositories, and it changes for reasons that are not always obvious. This guide explains what trending actually measures, how to interpret the numbers, and how to get the most out of the daily, weekly and monthly views on this site.
A common misconception is that GitHub Trending ranks repositories by their total star count. It does not. If it did, the same handful of giant, long-established projects (think frameworks with hundreds of thousands of stars) would sit at the top forever and the list would never change.
Instead, trending is about momentum: roughly, how many new stars a repository gained over a recent window relative to its normal baseline. A small project that picks up a few hundred stars in a single day because it was shared widely can easily outrank a famous project that gains the same number of stars but considers that an ordinary Tuesday. In practice this means trending surfaces what is newly interesting — fresh launches, viral tools, projects riding a news cycle — rather than what is merely large.
This site offers three time windows, and each answers a slightly different question:
| View | What it captures | Best for |
|---|---|---|
| Daily | Repositories gaining stars fastest in the last day. The most volatile and reactive view. | Catching brand-new launches and what is going viral right now. |
| Weekly | Momentum smoothed over seven days, filtering out single-day spikes. | Spotting projects with sustained, more-than-one-news-cycle interest. |
| Monthly | The slowest-moving view; rewards a full month of consistent attention. | Identifying durable shifts and tools that are becoming standards. |
A useful habit is to compare them: a repository that appears in all three views at once is showing both a spike and staying power — usually a stronger signal than a one-day wonder that tops the daily list and vanishes by the weekend.
A star is a bookmark plus a vote of interest. The total star count tells you how much cumulative attention a project has ever received. It is a lagging indicator — useful for context, but not what drives the ranking.
The "+N today" (or this week / this month) figure is the number that actually matters for
trending. It is the velocity — the recent gain — and it is what orders the list. When you are scanning for
what is hot, read this column first.
A fork is a personal copy of a repository, usually created to contribute changes or to build on top of the code. A high fork count relative to stars often signals a project that people are actively using and modifying, not just admiring — for example a template, a boilerplate, or a library with many contributors.
The global list is dominated by whatever is loudest across all of GitHub on a given day, which is frequently
JavaScript, TypeScript or Python. If you work in a specific stack, the language filter is the most valuable
control on the page: switch to Rust, Go, Java or another language and
the ranking is recomputed for that ecosystem alone. This is the difference between "what is trending
everywhere" and "what is trending in my world."
GitHub's official Trending page only ever shows the current moment. Once a day rolls over, yesterday's ranking is gone — there is no built-in way to ask "what was trending the week that framework X launched?" That makes trending oddly hard to study, despite being a rich record of the open-source zeitgeist.
This site keeps a snapshot of every day and backfills older days from the public Internet Archive, so the rankings become something you can revisit. You can scroll back through a calendar of archived days, watch a project climb and fade, or check what the community cared about on a specific date. Trends are far more interesting when you can see them over time rather than as a single frozen frame.
The figures shown here are captured at the moment each snapshot is taken and may lag GitHub's live data by a short while. GitHub does not publish the exact formula behind Trending, so any third-party description — including this one — is an informed explanation of observed behaviour rather than an official specification. This site is independent and not affiliated with or endorsed by GitHub or Microsoft; all repository names, descriptions and logos belong to their respective owners.