Where a star series comes from
- GitHub star history
- Exact, by day — GitHub's own star history, from the week the repository was created to the latest read. Unstars are already taken out, and it is read again on a schedule, so it keeps flowing. Every public repository is moving onto it.
- GitHub stargazer list
- Exact — one point per star, with its own timestamp. GitHub closed this list in July 2026, so a series read this way stops on a fixed date until gitdebt re-reads it from GitHub's star history.
- Historical star data
- Rebuilt from historical star data. Star actions are recorded and unstars are not, so it reads as an attention signal rather than a net star count, until gitdebt re-reads it from GitHub's star history.
- GitHub stargazer list, then historical star data
- One line, two methods, joined on a fixed date. The exact list runs up to the join and star activity continues after it, so the tail counts actions rather than current stargazers and does not record every star. Every chart built this way names the date it changes method.
Every chart names its source and its coverage date. None of them states how much of a history is missing: an archive series counts re-stars and can exceed a repository's own star total, so that figure would be wrong exactly where it looks most precise.
A repository with a prerendered page lives atgitdebt.com/owner/name; this route reads every other public repository live.