About this field guide
This is a gitforage portal, a small field guide to GitHub. Once a week it walks the topics below, looks closely at what is growing there, scores each find with plain rules, and brings home the ones it has not shown you before.
This portal is built from iacsha/gitforage-field-guide. Its interests file, its Keep and Leave it history and every past haul are in that repo.
What it forages for
A field guide for people who build, run and tinker with software.
It looks across open source for useful new tools and fast-growing projects: AI agents and local LLM tools, web frameworks, command-line and developer tools, databases, data and machine learning, security and privacy, Rust and Go, mobile apps, game development, self-hosted software, local-first home automation, and healthcare interoperability.
It prefers projects that are active, licensed and documented, and in the Get involved tab, maintainers who merge outside pull requests and answer issues.
Pick your patch to narrow it to the topics you care about.
Topics: llm, ai-agents, mcp, react, svelte, cli, devtools, terminal, database, postgresql, machine-learning, security, privacy, rust, golang, android, flutter, gamedev, godot, self-hosted, homelab, docker, home-assistant, fhir, hl7.
Projects it follows (their wild forks and kindred are foraged too):
- ollama/ollama
- modelcontextprotocol/servers
- sveltejs/svelte
- BurntSushi/ripgrep
- junegunn/fzf
- duckdb/duckdb
- godotengine/godot
- immich-app/immich
- home-assistant/core
- hapifhir/hapi-fhir
It lists repos described in English (and repos whose language it cannot tell); the language button shows or hides the rest on pages that have them. Repos whose stars look bought or botted (far more stars than forks, issues or contributors, or implausibly fast growth) are left out.
Where the finds come from
- Seedlings repos created recently in these topics and keywords.
- Thriving older repos gaining stars quickly, measured from star counts seen on earlier walks.
- Wild forks forks of followed projects that are ahead of upstream and recently pushed, often a revived version of a quiet project.
- Kindred repos that share the topics and words that are unusually common among the profile's stars and followed projects.
Reading a specimen card
Every card carries a specimen number (its place in the haul), its habitat (the main language) and the day it was found. The small tree ring beside the name is a cross-section of the repo: one ring for each year of its age, up to five, and an outer ring that is green when it grew this week, pale when it grew this month, amber when it has gone quiet and brown when it is dormant. A wider outer ring means it is gaining stars faster, the way a good year leaves a wide ring in a trunk.
The field note under the name is written by plain rules from the numbers gitforage measured: age, language, patch, how it was found and how its maintainers answer. It never borrows from the repo's own text. That text sits just below, in the maintainer's words, exactly as they wrote it.
How scoring works
Each rule adds points and a reason, and the score is the sum. The reasons are the tags on every card. Popularity is ranked within each topic and capped, so a small project that leads its niche can beat a big generic one. There is no machine learning and no paid placement: nothing here is sponsored.
Ranking by fit is not the same as predicting what will trend. The backtest (simulated) replays these rules on 26 past weeks and reports both what they caught early and what they missed.
Discover ranks useful tools on fit, adoption, activity, releases and license. Get involved also weighs maintainers who merge outside pull requests and answer issues, starter issues, and wild forks.
| Rule | Discover | Get involved | Points for |
|---|---|---|---|
topic_match | 3 | 3 | per interest topic the repo carries or was found by, up to 3 |
keyword_match | 2 | 2 | per keyword in the name or description, up to 3 |
star_velocity | 3 | 2 | stars a month for young repos, ranked within the topic (capped) |
stars | 1.5 | 1 | total stars for older repos, ranked within the topic (capped) |
star_growth | 2 | 1.5 | stars gained a month for older repos, measured between runs (capped) |
recent_push | 3 | 3 | pushed in the last 7 days; less for 30 or 90 days |
stale_push | -3 | -3 | no push for over a year |
release | 2 | 1 | a release in the last 90 days; half for the last year |
license | 1 | 1 | has a license |
readme | 1.5 | 1 | has a README, a description and a homepage |
affinity | 2 | 1.5 | shares the topics and words that are unusual among the profile's stars and seeds |
star_farm | -8 | -8 | penalty when the stars look inflated: far more stars than forks, issues or contributors, or implausibly fast |
feedback | 1 | 1 | nudged by Keep and Leave it marks on similar repos |
fork_ahead | 1 | 2 | a fork with commits ahead of upstream |
outside_prs | off | 1 | per pull request merged from outside contributors in 90 days, up to 5 |
issue_response | off | 3 | share of recent issues that got a reply or were closed |
contributing | off | 1 | has a CONTRIBUTING file |
good_first_issue | off | 1.5 | has open good first issue or help wanted issues |
Keep and Leave it
The Keep and Leave it buttons open a prefilled GitHub issue on this portal's repo. A workflow reads the title, records the mark in feedback.yml, replies and closes the issue. Marks nudge the ranking of similar repos (same topics, owner or language) on later runs.
Anyone with a GitHub account at least 30 days old can mark, up to 3 marks a day. A visitor's mark counts 0.25 of an owner's, and only an owner's Leave it hides a repo.
Privacy
Visits are counted with GoatCounter, which sets no cookies and collects no personal data. Nothing else on this site tracks you, and the site loads nothing from other hosts.
"Pick your patch" on the Discover page runs in your browser. Your picks, your "More like this" and "Hide" marks, and the topics found from your stars are kept in this browser's storage and nowhere else. "Use my GitHub stars" makes your browser ask GitHub's API for that user's public stars; gitforage never sees the username, and only the topics are kept. GitHub allows 60 such lookups an hour from one network. When you pick a pack or a topic, its name is counted as a GoatCounter event; nothing you type is sent.
Run your own
gitforage is free and MIT licensed. Start your own field guide in about five minutes: create a repo from the gitforage template, describe your interests in interests.yml, and turn on GitHub Pages. A weekly GitHub Action does the rest; there is no server and no paid key.