Reading your stats
What each number on your project's stats page means, where it comes from and what you can do with it.
Coding agents: read this page as markdown.
Every project you own has a stats page at /p/{your-project}/stats, linked
from the project page when you’re signed in. Only you can see it (and our
moderators, when they help you or look into abuse; each look is logged). The same
numbers are available to your agent at
GET /api/v1/projects/{slug}/stats?period=7d|30d|all, with a token that
has the read scope, and as CSV files for a spreadsheet.
What we count, and what we don’t #
- Every number is a total. You never see who looked at, upvoted, followed or saved your project, and breakdowns with fewer than 3 people in a group (a site that sent one visitor, say) are folded into “other”.
- Your own activity on your project is never counted.
- Days are UTC days. Numbers catch up within about five minutes.
- Pick the period at the top: the last 7 days, the last 30 days, or all time. For 7 and 30 days, each headline number says how it changed against the period before.
At a glance #
| Number | What it counts |
|---|---|
| Times seen | A release card at least half on screen for a second, anywhere on the site |
| Viewers | People who saw a card, counted once per hour (someone back the next day counts again) |
| Time on screen | How long a card stayed on screen, on average, when it was seen |
| Release opens | Clicks from a card to the release page |
| Release page views | Every visit to a release page, from anywhere: the site, a link on another site, your README. Bots aren’t counted |
| Repository clicks | Clicks to your repository or homepage |
| Shares | The share button on a card |
| Upvotes | Upvotes on your releases; weighted upvotes is what they count for in the ranking (below) |
| New followers | People who started following the project |
| New saves | People who saved the project to their list |
| Badge loads | Your README badge displayed (the snippet is on your project page). GitHub keeps a copy for a while, so the real number of README views is higher |
| Places won | Podium places on the day, week and month boards |
| GitHub stars | Stars at the last sync with GitHub, and how many were gained in the period (from the day we first see them) |
Release by release #
Each release shows its numbers for the period, then a closer look:
- Its place in the hot feed right now, and why: its upvotes, how people engage with it (time on screen, opens, clicks, shares, follows and saves, minus quick scroll-pasts), its momentum (the share of its views in the last 6 hours) and its age (a release counts half as much every 18 hours). New releases get a guaranteed number of views in the Fresh lane; the page says how many are left.
- Compared with recent releases: its rates since it was posted next to
the median of releases posted in the last 14 days, and how many of them
it beats. A release needs 20 views before it’s compared: fewer would be
noise.
- Open rate: release opens per viewer.
- Repository click rate: repository clicks per viewer.
- Upvote rate (vote score): weighted upvotes over weighted views, pulled toward the site’s average until there are enough views. It’s the score that decides the boards.
- Skip rate: of the times its card was shown, the share scrolled past in under a third of a second. Lower is better.
- First 48 hours: views per hour after you published it.
- How far people swipe: for releases with several screenshots, the share of viewers who reached each one. If few get past the first, put your best screenshot first.
- Screenshot checks: the hero screenshot’s quality checks, with what to fix (release requirements).
Boards #
For each board (day, week, month) the page shows where your best release of the open period stands: its rank, its weighted upvotes against the minimum needed to place, and the score to beat for the last podium place. A release competes in the period it was published in. How ranking works.
Upvotes, explained #
Each upvote counts by its voter’s weight. Brand-new or unproven GitHub accounts count for nothing at first and young ones partly, so a wave of fresh accounts can’t push a release up; established voters count fully, or a little more. The page shows how many of your upvotes fell in each group, and the sites voters came from.
Who looks, and from where #
- Signed in: the share of viewers with an account.
- Came back: signed-in viewers who had already seen an earlier release of yours.
- Where the cards were seen: the home feed, tag pages, the boards, your project and author pages, release pages, people’s following feeds.
- Sites that sent visitors to your release pages: the site only, never the page or the person.