GitHub Trending: Today — yt-dlp, Supabase, Fastify, Qbot, awesome-macOS

Strip the AI-hype reflex and today's GitHub Trending reads like the tabs you already have open: a downloader, a database, a web framework, a macOS app list. Here is the full board before the lens.

Nothing here launched this week

Four of these five repos are years old: yt-dlp dates to 2020, Fastify to 2016, awesome-macOS to 2015, Supabase to 2019. None is a fresh agent framework riding a demo video. They surface because something happened to them: a requirement changed, a dashboard got opened, a CVE landed. Trending today is a maintenance board, not a launch board. And the loudest maintenance story is a project being forced to grow a second runtime just to hold its ground.

yt-dlp/yt-dlp — the downloader that now needs a JavaScript engine

+273 stars today · 174k total · Python

It is the tool archivists, researchers, and offline commuters reach for to script media off YouTube and roughly 1,800 other sites. As of release 2025.11.12 it now requires an external JavaScript runtime for full YouTube support; without one, format availability is "limited, and severely so" for logged-in users. The cause is an arms race. YouTube's signature and n-parameter ciphers, plus its proof-of-origin tokens, grew past what yt-dlp's hand-written Python interpreter could execute, so the maintainers handed the entire n/sig solve to a real engine. Deno is the only runtime enabled by default; Node, Bun, and QuickJS work but stay off unless you opt in.

One commenter pushed on the engineering rather than the politics:

"Can anyone explain specifically what the YT code does that the existing python interpreter is unusable and apparently quickjs takes 20 minutes to run it?" — a commenter on the thread

The sharpest endorsement came not from a pirate but a paying customer whose official app had just failed him:

"I'm a paying YouTube premium subscriber. Last weekend, I wanted to download something so I can watch it on my way in the train. The app got stuck at 'waiting for download…' on my iPad. Same on iPhone. … Downloaded the video using yt-dlp." — a Premium subscriber whose official app stalled

The irony runs both ways: the tool Google spends engineering effort to block is also the one that delivered the download Google's own app could not.

UFund-Me/Qbot — an AI quant bot with a marketing problem

+47 stars today · 18k total · Jupyter Notebook

This one targets retail algo-traders who want a quant stack that runs entirely on their own machine: factor research, backtesting, and broker automation without renting a cloud platform. It packages Qlib-style strategy research and trade execution into one installable kit, paired with a paid "Pro" tier and a slimmed-down qbot-mini / iQuant spin-off promoted alongside the free repo. The community signal is the absence of one: no HN or Lobsters thread, no Bluesky conversation beyond a bare link. What discussion exists lives in the issue tracker, and its busiest open threads are people who cannot get it running — pip install failures on macOS, a "'gbk' codec can't decode" Unicode crash, "can't setup a valid environment on Windows 10". A repo with 18k stars whose top open issues are all installation errors is a particular kind of popular.

supabase/supabase — the open-source half of the Firebase alternative

+64 stars today · 105k total · TypeScript

Its audience is app and AI developers who want managed Postgres with auth, storage, realtime, and vector search bolted on: Firebase's convenience without surrendering SQL's portability. The differentiator is scope: the whole platform is self-hostable, including the Studio dashboard you would normally only get on the hosted plan. That open-sourcing is the move people still cite, and co-founder Paul Copplestone fielded it in the thread himself:

"We did a write-up on the tech stack and some of the approaches we considered for sharing code between our Platform and the Self-Hosted versions … We aim to get these to parity with each other." — Supabase co-founder Paul Copplestone

Parity between hosted and self-hosted is exactly the promise that keeps the Firebase-refugee crowd loyal: the exit door stays unlocked.

fastify/fastify — fast Node, now chasing web standards

+21 stars today · 37k total · JavaScript

Fastify is for backend teams who choose a framework on throughput and JSON-schema validation rather than ecosystem size — the people who left Express for the benchmarks. The recent motion is at the edges: maintainer Matteo Collina spent January experimenting with Web Standard API routes (fastify.web.*), which let handlers take standard Request/Response objects so front-end metaframeworks like React Router can sit on top. He closed the PR in favour of shipping it as a separate fastify-fetch plugin rather than bloating core. In parallel, the ecosystem patched a high-severity middleware-bypass CVE in @fastify/middie. Fastify has the quiet-incumbent problem: heavy production use, thin chatter. It is the framework people run, not the one they post about.

The tax of staying free

The through-line is not a language or a category, it is cost. yt-dlp makes the lesson sharp: keeping a free tool alive against a platform that does not want it there now means carrying a second language's runtime, pinned to exact versions and updated in lockstep with the adversary. That cost never shows up in a star count. It shows up the day someone's yt-dlp stops working because Deno isn't installed, and they learn the downloader they trusted quietly grew a dependency the size of a browser engine.