copperhead

Stats

GitHub Repository Traffic

33 days on the record, from 29 July 2026 to 30 August 2026.

Unique visitors429daily uniques, last 30 days
Unique visitorsUnique visitors, as recorded: 33 readings from 29 Jul 2026 to 30 Aug 2026, peaking at 33 on 29 Jul 2026.025503329 Jul 202630 Aug 2026
Page views3,266last 30 days
Page viewsPage views, as recorded: 33 readings from 29 Jul 2026 to 30 Aug 2026, peaking at 397 on 30 Jul 2026.025050039729 Jul 202630 Aug 2026
Unique cloners664daily uniques, last 30 days
Unique clonersUnique cloners, as recorded: 33 readings from 29 Jul 2026 to 30 Aug 2026, peaking at 93 on 30 Jul 2026.0501009329 Jul 202630 Aug 2026
Clones1,220last 30 days
ClonesClones, as recorded: 33 readings from 29 Jul 2026 to 30 Aug 2026, peaking at 262 on 30 Jul 2026.025050026229 Jul 202630 Aug 2026
Stars54cumulative
StarsStars, as recorded: 25 readings from 21 Jul 2026 to 27 Aug 2026, peaking at 54 on 27 Aug 2026.0501005421 Jul 202627 Aug 2026
Forks46cumulative
ForksForks, as recorded: 17 readings from 21 Jul 2026 to 31 Aug 2026, peaking at 46 on 31 Aug 2026.025504621 Jul 202631 Aug 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

ReferrerUniqueViews
github.com41459
docs.copperhead.sh815
linkedin.com611
Google511
copperhead.sh34
devesh.cv25
t.co22
x.com111
com.linkedin.android13
lnkd.in12

What they read

PathUniqueViews
repository home40132
/copperheadhq/copperhead3376
/copperheadhq/copperhead/issues/662027
/copperheadhq/copperhead/releases/tag/v0.10.01722
/issues1639
/pulls1364
/copperheadhq/copperhead/issues1033
/copperheadhq/copperhead/pulls939
/pull/236531
/pull/244350

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.