
When choosing a tool (especially an open-source one) to use, what's your thought process? What are the factors that matter to you?
Here's one obvious metric I'm sure you will also investigate: its GitHub stars.
You can't fully trust a project's GitHub stars alone. It is, however, a good way to determine if a tool is an adequate one and if it's likely to grow, if you use it correctly.
Even if a project has hundreds of millions of stars now, doesn't mean that it's still gaining popularity or maintained. Or if the project had an explosive breakout in the past? There's no way of knowing these simply from gazing at the stars count. Here's when Star History comes in handy: it shows how the number of GitHub stars of a project is increasing over the years. And - it's free and open-source.

To add a repo, type in the search bar and click View star history. Three input formats are supported:
https://github.com/star-history/star-historystar-history/star-historystar-historyFor something like hashicorp/terraform, you need to specify the full hashicorp/terraform since the org and repo names don't match.
You can also paste multiple repos at once, separated by commas.
After adding one repo, continue typing the next repo in the input box. They will all be rendered in the same chart.

Each repo appears as a pill-shaped badge below the input. You can:
Check Align timeline above the chart to switch from calendar time (Date mode) to days-since-first-star (Timeline mode). This lets you compare the growth trajectories of repos that started at different times.

Check Log scale to switch the Y-axis to logarithmic scale. This is useful when comparing repos with vastly different star counts โ it makes it easier to see growth patterns across different magnitudes.
Use the Legend radio buttons to place the legend at Top left (default) or Bottom right, depending on where the chart lines are.
Below the chart, you'll find these action buttons:
Star History reads star data from GitHub's star history API, which only answers authenticated requests. Any GitHub access token works, for any public repository, and a token also raises your API rate limit. The token needs no permissions or scopes at all.
Your token is stored only in your browser's local storage โ it is never sent to Star History servers.
Choose one:
Fine-grained token.
Classic token.
Then, on star-history.com, click Add access token in the header, paste your token, and hit Save.
The Show real-time chart on your README.md section below the chart generates a live chart image for your README.
<picture> element that follows the viewer's light or dark theme. Plain Markdown is a single image link for any Markdown renderer.The embed keeps your current chart settings โ repos, Date/Timeline mode, log scale, legend position โ and re-renders with the latest stars each time it is viewed.
We also have a Chrome extension. Install it, then go to any GitHub repo and click the extension icon โ a star history chart will pop up right there.
Play around and let us know @StarHistoryHQ what you think!
Bytebase- Database DevSecOps for Postgres, MySQL, Oracle, SQL Server, Mongo, Redis, and more.
