Every week I dig through GitHub Trending, Hacker News, and the corners of Reddit where maintainers actually talk, and pull out the open source projects and releases worth your attention. Here's a taste of Issue #1.

1. Main Thing — vercel/next.js

https://github.com/vercel/next.js

On 25 August Next shipped 16.3.3 (Active LTS) and 15.5.24 (Maintenance LTS) patching two unauthenticated RCEs — one hitting Windows-hosted servers, one in Image Optimization's AVIF handling. If you self-host, upgrade now: npm install next@16.3.3 (or next@15.5.24 on 15.x).

The other 4 picks this week — vercel/ai, firecrawl, archify, and Apache Maka — plus the "like / don't like / do this" breakdown on each, are in the full Issue #1 for members.

Join Commit Log free →

I spend way too many hours a week digging through GitHub Trending, HN, and OSS Discord servers. After doing this for a while, I've noticed the projects that go from 200 stars to 20k in a month almost always share the same three signals:

1. The README solves a problem in the first sentence.

Not "a flexible, extensible framework for..." — but "stop writing boilerplate for X." If you have to read past line 3 to know why you'd use it, most devs bounce.

2. Someone influential tries it and posts the result, not the announcement.

Launch tweets from the maintainer barely move the needle anymore. What actually spreads is a random dev posting "replaced [popular tool] with this and cut my build time in half" — with a screenshot.

3. Issues get responded to within hours, not days, in week one.

Early contributors are testing whether this is a living project or a drop-and-abandon. Fast, honest responses (including "not gonna fix that, here's why") build more trust than a perfect feature set.

None of this is about the code being good — plenty of great libraries die quietly, and plenty of rough-around-the-edges ones take off because the maintainer showed up.

I write up the ones doing this well every week over at Commit Log if you want the shortlist instead of digging yourself.