Stats
GitHub Repository Traffic
47 days on the record, from 29 July 2026 to 13 September 2026.
Unique counts are per day. A thirty-day figure adds those days up, so somebody who came back on Tuesday is counted again on Tuesday. Clones include CI: a workflow that checks the repo out on every run is a cloner, and a busy one outnumbers the people.
Where it came from
| Referrer | Unique | Views |
|---|---|---|
| copperhead.sh | 102 | 251 |
| github.com | 82 | 382 |
| docs.copperhead.sh | 54 | 184 |
| t.co | 43 | 75 |
| 29 | 66 | |
| linkedin.com | 23 | 31 |
| chatgpt.com | 10 | 10 |
| search.brave.com | 2 | 26 |
| Bing | 2 | 15 |
| symmetrical-giggle-rrgjgg97x9qfgp.github.dev | 1 | 14 |
What they read
Both tables are the trailing fourteen days, which is all GitHub will say about referrers and paths however long the record runs. Only the daily totals above accumulate.
GitHub shows a repository's traffic for the last fourteen days and then forgets it. Nothing recovers what fell off the back: there is no archive and no API for it, so the only way to have a year of the numbers is to have been writing them down all along. A job here snapshots the copperhead repo once a day and appends to a file that never rolls over. This is that file, drawn.
Collected by github-repo-stats, from the copperhead repo. The raw CSVs and a fuller rendered report live on this site's github-repo-stats branch, so every number here can be recomputed rather than taken on trust.