The problem is not “Trending this week as a mood.” The problem is GitHub velocity you can act on: REST snapshots over time, star/fork velocity, trend status breakout / rising / stable, interest groups, a personal watchlist with per-repo alert thresholds, paste-import of URLs, and acquire — clone on this VPS, mirror to GitLab, or both, with optional auto-sync. Dashboard: totals, top-10 7-day star velocity, last collection run, donut, language bars, Hot Now (created last 7 days, live, cached 1 hour). Feed: filters, 50/page, sortable velocity columns. Feed view still tries Telegram velocity alerts — tokens retired, so treat that as optional noise. Settings: interval, breakout threshold, clone dirs, per-user GitHub token, retention, groups. Manual import can queue to RRV. Kronos collection. Public landing; work is login. Not GitHub’s own explore page pasted as a screenshot.
Collection is a job. Acquire is a decision. Do not confuse them.
Not github.com/explore. Numbers are this tracker’s snapshots.
50/page. Telegram-on-view is best-effort.
This VPS disk is finite. Acquire is not a star.
Rate limits are real. Empty token means a slower shared path or failures — the landing will not hide that.
Will not scrape on the public landing. Will not pretend Telegram alerts still page you.
Pairs with RRV and ShipLog. Not a VC deal-flow CRM.
Cards match README features.
Login for /ght/app. This page is not your clone disk.
Open GHTRequires a MelTuc account. Create one free.
Intelligence dashboard for trending GitHub repositories with velocity tracking. Health stays cheap. If this page disagrees with the signed-in app, trust the app — the product contract and tests enforce that rule.