Break down any web page in one paste.

On this page 4 sections Close The signals that matter Triage a find in two minutes What to do with a find Most people discover a breakout repository when it is already on every timeline. By then the tutorials are written, the wrappers are built and the easy opportunities are taken. The signals show up earlier — in how fast stars arrive, who is opening issues, and which small communities are talking about it. This guide gives you a repeatable way to find those projects yourself. It takes about 30–45 minutes the first time and around 15 once it is a habit. Star velocity, not star count. 3,000 stars gained this week says more than 40,000 stars accumulated over five years. Recency. Created or first released in the last 30–90 days. Forks and outside contributors. Forks and issues from people other than the author mean someone is actually running it. Releases and commit rhythm. Tagged releases and steady commits separate a maintained project from a weekend demo. Conversation in small, technical communities. Show HN posts, niche subreddits and builder circles usually move before mainstream tech media. You can perform these seven research steps manually. Check each one off as you go — your progress is saved. 1 Search GitHub for young repos with momentum. Use GitHub's repository search with date and star qualifiers. Set the date to roughly three weeks ago and sort by stars: created:>2026-09-01 stars:>100 language:python Add topic: or language: to stay in your lane. Open the top 20 results in tabs. 2 Cross-check GitHub Trending. Open github.com/trending for today and this week , filtered to the languages you care about. Repos that appear in both lists are gaining momentum, not just spiking once. 3 Measure star velocity. Divide stars by the repo's age in days, or look at the curve on star-history.com . A steep, recent curve is the signal. You can pull the numbers straight from the GitHub API: BASH COPY # Stars per day since creation for one repo (needs curl + jq). # Unauthenticated requests are limited to 60/hour; set GITHUB_TOKEN for more. curl -s -H "Accept: application/vnd.github+json" \ | ((now - ($r.created_at | fromdateiso8601)) / 86400) as $days | {repo: $r.full_name, stars: $r.stargazers_count, forks: $r.forks_count, open_issues: $r.open_issues_count, age_days: ($days | floor), stars_per_day: (($r.stargazers_count / ([$days, 1] | max)) | floor)}' 4 Check that real people are using it. Look at the Issues and Pull requests tabs. You want bug reports and questions from many different accounts, merged PRs from outside contributors, and at least one tagged release. A repo with thousands of stars and no issues deserves suspicion. 5 Find where it is being discussed. Search the repo name and URL on hn.algolia.com , Reddit (subreddits like r/LocalLLaMA, r/selfhosted or r/MachineLearning, depending on the topic) and X. Read the comments: the complaints and feature requests are a map of what to build next. 6 Answer “why now?” Write one sentence on what this makes possible that was hard last month. Is it riding a new model release, a new API, a price drop? If you cannot answer, it is probably noise. 7 Log it and re-check in 72 hours. Keep a simple sheet: repo, date found, stars, stars/day, why now, idea. Re-check after three days. Sustained velocity moves it to your shortlist; a one-day spike drops off. Triage a find in two minutes Paste the README and the numbers from step 3 into your AI assistant with this prompt: PROMPT · REPO TRIAGE COPY PROMPT You are helping me evaluate an early-stage open-source project. Stats: [stars], [stars/day], [forks], [age in days], [open issues], [latest release] 1. In two sentences: what does it do and who is it for? 2. What is genuinely new here versus existing tools? Name the closest alternatives. 3. What would stop a normal developer from using it today (setup, hardware, missing docs)? 4. Red flags: signs of hype without usage, licensing issues, abandoned maintenance. 5. Three concrete things I could build, write or offer on top of it this week. Be specific and skeptical. If the README does not support a claim, say so. What to do with a find Write the explainer — the first clear “what it is and how to use it” post often ranks and gets shared for months. Build on it — a hosted version, an integration, a template or a UI for a CLI-only tool. Contribute — docs and examples are welcome in young projects and put your name next to something rising. If a find has a real business behind it, the next Blueprint shows how to turn it into a product: Turn an Open-Source Project Into a Paid Product How people build real products on top of open-source software: reading the license correctly, finding the painful part users will pay to skip, choosing a business model, and launching without burning goodwill. Blueprint · 4 min MEMBERS (locked) Want us to find them for you? GitHub Discovery automatically finds and ranks fast-growing repositories, so you can spend your time creating the content instead of doing hours of research. Included with The AI Stack: tools, blueprints, source code and the community. See everything in The AI Stack Get a link to this guide in your inbox to come back to later.