DEV Community: lan yi

GitHub Star History Is Restricted. Here Is a Better Way to Read Repository Activity.

lan yi — Sat, 08 Aug 2026 07:01:16 +0000

GitHub has restricted detailed stargazer access. Learn why Git commit history is a more useful way to evaluate repository activity, maintenance, and development momentum.

For years, GitHub stars have been one of the fastest ways to judge an open-source repository.

You find a package, notice that it has 20,000 stars, and naturally assume it is popular, trustworthy, and actively maintained. Sometimes that assumption is correct. But stars only tell part of the story. They measure attention, not necessarily ongoing work.

That distinction matters even more now that GitHub has restricted access to detailed stargazer information. The public list of people who starred a repository, including the timestamps needed to reconstruct a star-growth timeline, is no longer broadly available through GitHub's stargazer endpoint. Access is limited to repository admins and collaborators. The total star count remains public, but the detailed historical trail behind that number is no longer a dependable data source for tools that analyze arbitrary public repositories.

This change makes one thing clearer: when you want to understand whether an open-source project is alive, stars are not enough. Commit history is often the better signal.

Why GitHub star history was never the full picture

Stars are valuable. They can show that a project has attracted attention from developers, appeared in a popular newsletter, or solved a problem that resonates with a large audience. They are useful as a rough popularity metric.

However, a star is usually a one-time action. A repository can gain thousands of stars during a launch, a viral social-media post, or an appearance on a curated list, then receive very little maintenance afterward. The number stays visible and continues to look impressive even if development has slowed down.

Star history can make this slightly easier to interpret because it reveals when attention arrived. A sudden spike may correspond to a launch or a trending post. Steady growth may suggest continued discovery. But even a perfect star chart does not show what the maintainers are actually building today.

For that, you need to look at the codebase's activity.

What commit history can tell you

Every commit represents a recorded change in a repository. Taken together, commits create a timeline of development that is closer to the day-to-day reality of a project.

Commit history can help answer practical questions such as:

Is the project receiving recent maintenance?
Are maintainers releasing fixes regularly or only occasionally?
Has there been a major refactor, migration, or new feature push?
Is development accelerating, stabilizing, or becoming quiet?
Does the repository show a consistent working rhythm over time?

No single metric can answer all of these questions. A project may intentionally have few commits because it is mature and stable. Another may have many commits because it is still experimental. Context always matters.

Still, commit activity gives you direct evidence of work happening in the repository. It is far more informative than a star total when you are comparing dependencies, reviewing a project before adoption, or trying to understand its current momentum.

From a long commit list to an activity chart

GitHub already exposes commit history, but reading it is often tedious. You have to scroll through pages of commit messages, compare dates manually, and infer the significance of additions and deletions one entry at a time.

GitStock makes that process visual.

GitStock turns the recent commit history of a public GitHub repository into an interactive chart inspired by market activity charts. Each commit becomes a point in a timeline, using code additions and deletions to make the scale of change easier to see.

Instead of asking only, "How many stars does this repository have?", you can explore questions like:

When did the most substantial changes happen?
Has the project been actively updated in recent weeks or months?
Are there distinct periods of rapid development?
Did a large release or refactor change the shape of the codebase?

The result is not a replacement for code review, release notes, or maintainer documentation. It is a fast first view of a repository's development story.

What is GitStock?

GitStock is a free GitHub commit history visualizer for public repositories. It takes the latest 100 commits from a repository's default branch and presents them as an interactive, left-to-right K-line-style activity chart.

The chart uses each commit's additions and deletions to show both the rhythm and the relative size of code changes. This makes it easier to notice a concentrated development sprint, a major refactor, a period of regular maintenance, or a long quiet stretch that would be hard to spot in a flat commit list.

Using GitStock does not require a GitHub login or a personal access token. Enter an owner/repository path, such as gin-gonic/gin, or paste a public GitHub repository URL. GitStock generates the activity view and lets you replay the timeline, inspect individual commits, and share the result as a page link, SVG image, Markdown embed, or video.

Start here: gitstock.org.

Stars show attention. Commits show progress.

The restriction on detailed GitHub stargazer data is a useful reminder to avoid relying on a single public metric.

Stars still matter. They can help people discover useful projects and provide a signal of broad developer interest. But a high star count should be the beginning of an evaluation, not the end of it.

When you need to understand the current state of a project, its commit history offers a more immediate view of ongoing work. It shows whether the repository is changing, when it changed, and how the development pace has evolved.

That is the problem GitStock is built to solve.

Paste any public GitHub repository into GitStock to turn its recent commit history into a clear, shareable activity chart. Whether you are evaluating a dependency, tracking an open-source project, or simply curious about how a repository has evolved, GitStock helps you see the work behind the code.

Frequently asked questions

Can I still see a repository's total GitHub stars?

Yes. The public star count remains visible. What is restricted is the detailed list of stargazers and the timestamps that can be used to build a full star-history timeline for repositories where you are not an admin or collaborator.

Is commit history a perfect measure of project quality?

No. Commit frequency alone does not prove quality, security, or suitability. It is one useful signal that should be considered alongside documentation, releases, issue activity, community health, tests, and your own technical requirements.

What can GitStock visualize?

GitStock visualizes the latest 100 commits, additions, and deletions from a public GitHub repository's default branch as an interactive activity chart. You can replay the timeline, inspect individual commits, and share the result with a page link, SVG image, Markdown embed, or video. Try it at gitstock.org.

Why use GitStock instead of reading commits directly on GitHub?

GitHub's commit list is excellent for inspecting individual changes. GitStock complements it by showing the overall pattern of activity, so you can understand development momentum before diving into individual commits.

I Built GitStock: View Git Hub repositories like you would view stock prices.

lan yi — Fri, 26 Jun 2026 09:33:45 +0000

GitHub tells us a lot about a project, but the signal is often spread across commit history, graphs, files, and activity pages.

I wanted a faster way to answer a simple question:

How active does this repository feel at a glance?

So I built GitStock, a small developer tool that turns any public GitHub repository into a market-style candlestick chart.

What is GitStock?

GitStock renders GitHub repository activity like a stock chart.

Enter a public repo such as:

github.com/tailwindlabs/tailwindcss

GitStock fetches recent commit data and turns commits, additions, and deletions into an interactive SVG K-line chart. Each candle represents repository movement, making code activity easier to scan visually.

Instead of reading a long commit list, you get a compact activity chart that helps you spot:

bursts of development
quiet periods
large code changes
overall project momentum
whether a repo feels actively maintained

Why candlestick charts for GitHub?

Candlestick charts are great at showing movement over time. In financial markets, they help people quickly understand volatility, momentum, and direction.

Open source projects have similar patterns.

Some repositories move steadily. Some have sudden bursts. Some go quiet. Some receive large rewrites or heavy maintenance waves.

GitStock brings that visual language to code activity.

It is not trying to replace GitHub Insights or deep repository analysis. It is meant to be a fast visual layer that makes repo activity more readable and more shareable.

What you can do with it

GitStock currently supports:

generating charts for public GitHub repositories
rendering commit activity as SVG candlestick charts
mapping additions and deletions into chart movement
viewing commit details through interactive SVG tooltips
copying the chart as HTML
copying the chart as Markdown
copying the chart image
copying a direct image URL

That makes it useful for README badges, launch posts, project reports, dashboards, newsletters, and quick comparisons between repositories.

A chart you can actually share

One thing I wanted from the beginning was simple sharing.

When you generate a chart, GitStock gives you copy buttons for:

HTML embed code
Markdown embed code
image copy
image URL

So if you maintain an open source project, you can add a live-looking activity chart to your README or documentation without taking screenshots manually.

Who is this for?

GitStock is built for:

open source maintainers who want to show project activity
developers evaluating whether a repo is alive
founders and builders tracking technical momentum
writers creating posts about open source projects
investors and analysts looking for quick developer-signal visuals
anyone who enjoys seeing code activity from a different angle

How it works

Under the hood, GitStock uses GitHub repository commit data, including additions and deletions, then renders the result as an SVG chart.

The app is built with Go and Gin on the backend. Charts are generated server-side, cached, and served as SVGs so they are lightweight and easy to embed.

The goal is to keep the experience simple:

Enter a public GitHub repository.
Generate the chart.
Copy or share it.

No dashboard setup. No account flow. No complicated configuration.

What I learned building it

The most interesting part was translating commit history into a chart model that feels natural.

A commit is not a stock price, but it does have movement:

additions increase the codebase
deletions reduce it
large changes create wider swings
sequences of commits create momentum

Once represented visually, repositories start to feel surprisingly different from one another.

Some charts look calm and consistent. Others look volatile. Some show long quiet stretches followed by big bursts of work.

That is the part I find fun: GitStock makes repository activity feel visible.

Try it

If you work with GitHub projects, try GitStock with a repo you care about:

https://gitstock.org

Try your own project, a favorite open source repo, or a library you depend on.

I would love feedback on:

which repositories produce the most interesting charts
what signals should be added next
whether stars, releases, issues, or PRs should become chart overlays
how the embed experience could be improved

GitHub activity already contains a lot of useful signal. GitStock is my attempt to make that signal easier to see, share, and talk about.

Things You Should Know Before Starting Indie Development

lan yi — Sat, 09 May 2026 12:01:55 +0000

Apple Small Business Program

If your annual revenue is under 1 million USD, you can join Apple's Small Business Program and reduce the App Store commission rate from 30% to 15%.

That means if a user pays 10 dollars, you would receive 8.5 dollars instead of 7.

As long as your annual proceeds stay below 1 million USD, the lower rate continues. If you go above 1 million USD in a given year, the commission returns to 30% for the rest of that year, and you will no longer qualify for the program in the following year.

Both individual and company developer accounts can apply.

Apply here: https://developer.apple.com/app-store/small-business-program/enroll/

Cloudflare Startup Program

The credits can be used for the services below and are valid for one year.

This is especially useful if you want to build the backend for a website or app.

Databases and Storage

R2
Workers KV
Queues
D1

Compute

Workers
Workers for Platforms
Durable Objects
Workflows

AI

Workers AI
Vectorize

Media

Images and transformations
Stream
Cloudflare Calls

Performance and Security

Argo
Load Balancing
Cache Reserve

UI/UX Skill

This is currently the most starred UI skill project. It can be used to guide AI when generating app or website interfaces.

https://github.com/nextlevelbuilder/ui-ux-pro-max-skill

App Submission

When uploading screenshots in App Store Connect, it often reports that the image size is incorrect. You need to crop according to the exact size shown in the error message.

These two tools can crop images directly to the dimensions required by App Store Connect.

Preview and screenshot crop tool:
https://app-icon-generator.com/tools/apple-screenshot-preview-capture-tool

In-app purchase review screenshot crop tool:
https://app-icon-generator.com/tools/in-app-purchase-review-screenshot-crop-tool

Apple Search Ads

After your app goes live, you can run ads for it on the App Store through Apple's ad platform. New users usually get 100 USD in ad credit, which is worth claiming.

Eligibility

As long as you meet the following conditions, you can qualify whether your account is personal or company-owned:

New user: You must be registering an Apple Search Ads account for the first time.
Developer status: You must be the Account Holder of a registered App Store Connect account.
Published app: At least one app under your account must already be live on the App Store.
Account linking: Your Apple Search Ads account must be linked with your App Store Connect account.

How It Works

The credit is usually added automatically, but you still need to complete the basic setup:

Add a valid payment method, such as a credit card, in Apple Search Ads.
The system will consume the 100 USD credit first. Only after that is exhausted will it start charging your card.

https://app-ads.apple.com/