Skip to content

Latest commit

 

History

History
43 lines (28 loc) · 3.33 KB

HOW_IT_WORKS.md

File metadata and controls

43 lines (28 loc) · 3.33 KB

English | 简体中文 | 繁體中文 | 日本語 | 한국어

How GitHub Risers works

← Back to the rankings

Total-star lists keep the old giants on top and bury what is taking off right now. GitHub Risers ranks repos by stars gained per day (last 7, 30 and 365 days) and groups them into categories, with AI as the main board. Every category has a hottest-new-repos board for repos created in the last 7 days, then week, month and year star-growth rankings, and total stars last. All numbers come straight from the GitHub API. Classification rules: docs/CATEGORIES.md.

Updated daily. Each update is archived.

Each board in the README shows the top 10. The full top 20 of each board (from 70 tracked projects) is in the latest/ files.

These tables are the latest ranking. Every update is also saved per time slot: ranking history · latest/rankings.md.

The #1 of every board in every category, generated by script from the data below. n/a means that board has no entry in this run.

Categories

AI ★ primary LLMs, agents, MCP, coding copilots and generative AI
Developer Tools CLIs, editors, package managers, linters and build tooling
Security Vulnerability scanners, SAST, supply-chain and runtime security
Web / Frontend Frontend frameworks, UI kits, CSS and browser tooling
Infrastructure Containers, Kubernetes, cloud, networking and observability
Design / Creative Design systems, drawing, animation and creative tooling
Data Databases, analytics, ETL and data engineering

Hottest new repos (created in the last 7 days)

Repositories created within the last 7 days in this category, found with the GitHub search API (by topic: a repo must carry one of the category's topics) and ranked by stars per day since creation. A repo that appears in this category's other rankings (or is a tracked project here), or that already claimed a slot in an earlier category (AI first), is left out. Descriptions are the repo's own GitHub description; translations live in data/translation_library.json. Rules: docs/NEW_ARRIVALS.md.

How the numbers are produced

  • Total stars: GET /repos/{owner}/{repo} → stargazers_count.
  • Stars gained: GET /repos/{owner}/{repo}/stargazers/history (GitHub's privacy-safe weekly/daily star counts). The gain is the sum of the N complete UTC days before today (today is excluded). Stars/day = gain ÷ N.
  • GitHub states that week/day bucket boundaries are not guaranteed to align with UTC, and stars that were later removed are not counted, so the figures can be off by a small amount at the window edges.
  • Star history curves are star-history.com SVG images embedded by URL. This repo contains no analytics or tracking script of any kind.
  • The raw numbers are in data/stats.json; daily snapshots of the star count are appended to data/stars.json.

Contributing

Add an entry to data/projects.json (with category and desc in all five languages), then run python tools/update_stars.py. Categories: docs/CATEGORIES.md. Daily updates: docs/DAILY_UPDATE.md.