copperhead

Stats

GitHub Repository Traffic

79 days on the record, from 29 July 2026 to 15 October 2026.

Unique visitors1,526daily uniques, last 30 days
Unique visitorsUnique visitors, as recorded: 79 readings from 29 Jul 2026 to 15 Oct 2026, peaking at 273 on 15 Oct 2026.025050027329 Jul 202615 Oct 2026
Page views4,160last 30 days
Page viewsPage views, as recorded: 79 readings from 29 Jul 2026 to 15 Oct 2026, peaking at 549 on 8 Sept 2026.05001.0k54929 Jul 202615 Oct 2026
Unique cloners884daily uniques, last 30 days
Unique clonersUnique cloners, as recorded: 79 readings from 29 Jul 2026 to 15 Oct 2026, peaking at 121 on 27 Sept 2026.010020012129 Jul 202615 Oct 2026
Clones1,774last 30 days
ClonesClones, as recorded: 79 readings from 29 Jul 2026 to 15 Oct 2026, peaking at 289 on 26 Sept 2026.025050028929 Jul 202615 Oct 2026
Stars588cumulative
StarsStars, as recorded: 68 readings from 21 Jul 2026 to 16 Oct 2026, peaking at 588 on 16 Oct 2026.05001.0k58821 Jul 202616 Oct 2026
Forks126cumulative
ForksForks, as recorded: 44 readings from 21 Jul 2026 to 16 Oct 2026, peaking at 126 on 16 Oct 2026.010020012621 Jul 202616 Oct 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
t.co213237
github.com77128
copperhead.sh3843
Google3444
docs.copperhead.sh1417
linkedin.com1215
com.linkedin.android911
search.brave.com55
teams.public.onecdn.static.microsoft46
devbisme.github.io24

What they read

PathUniqueViews
/copperheadhq/copperhead533717
/copperheadhq/copperhead/issues78193
/copperheadhq/copperhead/pulls38154
/copperheadhq/copperhead/issues/663854
/copperheadhq/copperhead/fork2628
/copperheadhq/copperhead/graphs/contributors2021
/copperheadhq/copperhead/commits/main1124
/copperheadhq/copperhead/pull/365931
/copperheadhq/copperhead/pull/381737
/copperheadhq/copperhead/pull/367626

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.