TrendingRepo's trend score is deterministic and inspectable. Every input, weight, and decay constant lives in this document. No secret sauce. The pipeline is open source — link at the bottom.
Stars gained in the last 24h. The primary signal — momentum on the canonical platform.
Count of distinct discussions on Hacker News, Bluesky, Lobsters, dev.to, and ProductHunt. Multiple sources stack — three or more active platforms talking is the breakout signal.
Combined score of comments, upvotes, and retweets per mention. A mention with 200 comments outranks a mention with 2.
A star burst 1h ago counts more than one 23h ago. The half-life is 6h — we are scoring acceleration, not history.
Each category (devtools, AI, frontend, infra…) has its own median. Raw scores are normalized against that median — otherwise everything in AI would look like it's trending.
A repo earns the BREAKOUT tag when its 24h score lands more than 3× over its 7-day rolling median and at least three distinct sources are talking about it inside the window. Both conditions matter:
The trending pipeline runs every 20 minutes (UTC :07, :27, :47). Mention pipelines run on per-source schedules — each source has its own rate limits and we respect them:
Every repo's detail page (e.g. /repo/vercel/next.js) shows the raw signal breakdown — per-source mention counts, star deltas across windows, and the live trend score with every weighted input visible. The pipeline source is on GitHub: