Group trends

Topics

Weekly share of the stars each group gained, for the 6 groups with the biggest gain over the last 8 weeks. A line is that group's share of all measured stars that week, not a raw star count. Cooling: latest share at or below 0.7× the early share. Heating: at or above 2×. Both need at least 3000 stars in the early 8 weeks and 20+ measured repositories. A range of 52 weeks draws 51 points, because the first week has no week before it.

Collections

Measured exactly as in Topics above: same weeks, same coverage caveat, same cooling and heating rules.

Trending rank movement

Rank on the three GitHub trending pages the pipeline scrapes, each period compared between its own two most recent captures. GitHub overwrites that page between scrapes, so this comparison exists only because the pipeline stores the rank of every repository it saw before writing the new one. The panel does not follow the time range above, it is always about the trending pages as they stand now, and these are the all-language pages: each section links to the ranking list, where every card carries its own up or down badge for its own period.

What this view cannot tell you

• Only repositories with weekly history are counted, and coverage is uneven: each row prints measured against total. A line drawn from a small part of a group can move for reasons unrelated to the group.
• Membership is today's tags applied to the whole period. The pipeline rewrites tags every run and keeps no history, so a line means repositories tagged this way today, not who carried the tag then.
• The early and recent windows are always the first and last 8 weeks of the chosen range, so the same group can look cooling over six months and heating over a year. The two are answering different questions.
• Weekly, not daily: a spike that lasted three days inside one week is invisible here, and a repository only enters the series once it is tracked.
• Stars removed by GitHub after the fact (spam purges) are subtracted from the rebuilt history, so a week's figure is what the repository shows now, not what was reported at the time.
• Numbers move between visits while the history backfill is still filling in, so a group can enter or leave the cooling and heating lists without anything about the group changing.