GitHub stars history shows you how a project grew, not just how much. It's the difference between knowing a repo has 10k stars and knowing it got 8k of them in a single week after a Hacker News post.
This guide covers every method to track GitHub star history, how to read the data, and how to use it to grow your own project.
What Is GitHub Stars History?
GitHub stars history is the timestamped record of when each star was added to a repository. Unlike the current star count (visible on any repo), the history shows the growth curve over time — revealing launch spikes, viral moments, plateau periods, and organic growth trends.
Why it matters:
- Spot the exact distribution channels that drove your biggest spikes
- Compare your growth trajectory against competitors
- Identify plateau periods before they become stagnation
- Demonstrate traction to investors with a visual growth story
How to Track GitHub Stars History
Method 1: star-history.com (Free, No Code)
The fastest way to visualize any repo's star history.
- Go to star-history.com
- Type any GitHub repo name (e.g.
toeverything/AFFiNE) - Get an instant interactive chart — no signup required
- Compare up to 5 repos on the same chart
- Embed the chart directly in your README with one line of markdown
Best for: Quick visual checks, README badges, investor decks.
Method 2: GitHub API (Raw Timestamped Data)
For developers who want the full dataset:
curl -H "Accept: application/vnd.github.v3.star+json" \
-H "Authorization: Bearer YOUR_TOKEN" \
"https://api.github.com/repos/OWNER/REPO/stargazers?per_page=100&page=1"
Each response item includes:
-
starred_at— exact ISO timestamp when the star was added -
user— the GitHub user who starred
Paginate through all pages to get the complete history. For large repos (10k+ stars), this can take several minutes.
Best for: Building custom dashboards, exporting to CSV, automated monitoring.
Method 3: OSS Insight (Free, Analytics-Grade)
OSS Insight provides deeper analytics than star-history.com:
- Star growth by geography
- Contributor activity correlation with star growth
- Comparison with similar repos in the same category
- Historical trend data going back years
Best for: Detailed analysis, understanding who is starring your repo.
Method 4: GitHub Insights (Repo Owners Only)
If you own the repo, the native GitHub Insights tab shows:
- Stars over the past 14 days
- Traffic sources (where visitors came from)
- Top referring sites
Limitation: Only 14 days of data, and only accessible to repo admins.
How to Read Star History Charts
The Growth Patterns That Matter
Healthy organic growth:
A steady upward slope with small bumps. This means the project is finding new users consistently through search, word of mouth, and community mentions. No single spike dominates the chart.
Launch spike + plateau:
A sharp vertical jump (launch day) followed by a flat or slowly rising line. Common for projects that launched well but haven't built a content or community engine. The flat line is a warning sign.
Multiple spike pattern:
Several distinct spikes at irregular intervals. Each spike is a "relaunch moment" — a HN post, a viral tweet, a conference talk. This is the pattern of projects that consistently re-activate distribution. AFFiNE's star history shows this pattern: 8-10 distinct spikes over 18 months, each from a different channel.
Vertical cliff:
Stars drop suddenly. Almost always means a bot-star purge by GitHub (they periodically remove inauthentic stars). Legitimate projects rarely lose real stars.
Spike Attribution: Finding Your Best Channels
When you see a spike in your star history, cross-reference the date against:
- Hacker News posts (news.ycombinator.com/submitted?id=yourusername)
- Twitter/X mentions (search:
github.com/yourrepo) - Reddit posts (search: site:reddit.com yourrepo)
- Product Hunt launches
- Blog posts and tutorials mentioning your project
The spike source with the highest star-to-effort ratio is your primary distribution channel — double down on it.
GitHub Stars History vs. Star Velocity
Total stars = vanity metric for established projects
Star velocity = what actually matters for growth-stage projects
Star velocity = stars gained per week (or month), smoothed over a rolling average.
A project with 2k stars growing at 500/week is far more interesting than a project with 20k stars growing at 50/week. Star velocity is what GitHub's trending algorithm rewards.
Tools to track velocity:
- GitStar Ranking — shows daily and weekly velocity
- GitHub API — calculate yourself: (stars at time T) - (stars at time T-7 days)
- star-history.com — the slope of the curve is a visual proxy for velocity
Using Star History Data to Grow Your Repo
The playbook from growing AFFiNE to 60k+ GitHub stars:
- Identify your spike sources — which channels drove your 3 biggest spikes? Build a repeatable process around the top one.
- Set a velocity target — pick a weekly star goal (e.g., 100 stars/week) and reverse-engineer how many HN posts / Reddit posts / tweets it takes to hit it.
- Schedule relaunch moments — don't rely on organic growth alone. Plan 1-2 "relaunch" events per month: a major feature release, a blog post, a community event.
- Track competitor velocity — if a competitor's star velocity is accelerating, investigate what they just shipped or where they just appeared.
- Use star history in your pitch — a chart showing consistent growth is more compelling than a static "10k stars" number.
Star History Tools Comparison
| Tool | Data depth | Real-time | Compare repos | Price |
|---|---|---|---|---|
| star-history.com | Full history | Yes | Up to 5 | Free |
| OSS Insight | Full history | Near real-time | Yes | Free |
| GitHub API | Full history | Yes | Manual | Free |
| GitHub Insights | 14 days | Yes | No | Free (owners only) |
| GitStar Ranking | Velocity only | Daily | Yes | Free |
FAQ
How far back does GitHub star history go?
All the way to the first star. GitHub has stored star timestamps since the feature launched. You can retrieve the complete history via the API for any public repository, regardless of age.
Can GitHub stars be faked?
Yes, star farms exist. Signs of fake stars: vertical spikes with no corresponding community activity, stars from accounts with no other activity or followers, star gains at unusual hours (e.g., 3am local time). GitHub periodically purges inauthentic stars, which causes the "cliff" pattern in some repos' history.
Does star count affect GitHub search ranking?
Yes — star count and recent star velocity both influence how repos surface in GitHub's own search results and trending page. More stars → more discoverability → more organic stars. This is the core flywheel.
For the complete open source growth playbook — including how to systematically drive star growth through community, content, and launch strategy — see github.com/Gingiris/gingiris-opensource.
Written by Iris — grew AFFiNE from 0 to 60k+ GitHub stars. Follow @Iris_carrot for open source growth tactics.
Top comments (0)