📡 GitHub Radar
A weekly radar of trending GitHub repos, AI first, each with a one-line
summary and a sharp take.
A read-mostly Next.js site over the Notion archive that a set of Claude Code
routines writes every week. The site never calls GitHub itself.
🌐 What it shows
| Page | Source table | Shows |
|---|
/ | Trending + Blog + Loot | Dashboard: the top five hot repos, the latest blog posts, and, for the signed-in owner only, one summary card per loot ledger |
/trending, /trending/[id] | Trending Archive | Weekly trending repos, AI first, filterable by category, with 新上榜 / 在榜週數 badges; one page per repo |
/blog, /blog/[id] | Blog Archive | AI and agent blog posts grouped 官方 / 個人, each with a summary and a 點評, newest first |
/ask | none (radar-rag) | Ask the radar: questions in Chinese or English, answered from the Trending and Blog archives with citations that link to the detail pages here |
/api/latest-week | Trending Archive | JSON: the latest week's top three repos (repo, link, stars/week, momentum, summary, take), ranked like the dashboard; feeds the owner's GitHub profile README |
/loot/[target], /loot/[target]/[id] | Loot Ledger (claude / copilot / opencode / codex) | Owner only. Config assets worth stealing into each coding agent's setup, grouped by status, with an editable status |
The site is in Traditional Chinese. Every per-repo signal it shows, and the rule
that produces it, is in docs/signals.md.
🔧 How it works
flowchart LR
Routines["Claude Code routines<br/>(private repo)<br/>weekly / daily"]
Notion[("Notion<br/>archive tables")]
Server["Next.js server<br/>reads cached 600 s"]
Pages["Public pages<br/>/ · /trending · /blog"]
Ask["/ask<br/>(browser)"]
Rag["radar-rag<br/>POST /ask"]
Gate{"/loot/*<br/>password gate"}
Owner["Owner"]
Routines -->|"write rows"| Notion
Notion -->|"data_sources query"| Server
Notion -->|"POST /sync (weekly)"| Rag
Server --> Pages
Ask -->|"question + Turnstile token"| Rag
Server --> Gate
Gate --> Owner
Owner -->|"set loot Status"| Server
Server -->|"PATCH page"| Notion
- Data is written upstream. The routines that scout GitHub and the AI blogs,
enrich each repo and write the Notion rows live in a separate, private
repository. This site only reads those tables.
- One write path. The owner can change a loot row's
Status from the UI. It
is a password-gated Server Action that patches that one Notion page and busts
that ledger's cache, so a reload shows the new value.
- Server-side only. Every Notion call runs on the server with an internal
integration token; the token never reaches the browser.
The agents upstream, how their writes are bounded, and what broke in production
are written up in docs/case-study.md.
The same Trending Archive and Blog Archive also feed radar-rag,
a Java / Spring AI service that answers questions over them, in Chinese or English, with
citations back to the rows it used. The site's /ask page is its front end. The page's
browser code calls radar-rag directly, while the site's server still reads only Notion.
🔐 Access
The dashboard, /trending, /blog and /api/latest-week are public. /loot/* sits behind a
single-password gate, because the Vercel free tier cannot password-protect a
production deployment, so the gate lives in the app:
proxy.ts redirects any /loot/* request without a valid session
to /login. The loot pages check the session again before reading a ledger,
so a request the proxy matcher misses still gets no data.- A successful login sets a 30-day, HTTP-only session cookie holding an
HMAC-signed expiry. The signing secret never leaves the server.
- The status-write Server Action checks the session again, because Server
Actions POST to their own route and the proxy does not see them.
Signed out, the dashboard renders without the loot summary and the nav has no
Loot tab, so anonymous visitors never receive loot data.
🏃 Run it yourself
[!NOTE]
This is a personal dashboard. It renders tables that a private set of
routines fills, so a fresh clone has nothing to show until you point it at
Notion tables with the same schema. The columns each page reads are the
*_PROPS maps in lib/data.ts; a page whose first row lacks
one of them shows an error naming the column rather than rendering blanks.
This is the beginning of the README. Read the rest at the original. Read the full README ↗
