📊 Live Telemetry
Pages Analytics
Nightly snapshot of every repo and hosted site in the toolkit. GitHub Traffic API (rolling 14 days per call, merged into a year-to-date daily series) for repos · Microsoft Clarity for hosted sites · long-memory daily data stored beyond GitHub's 14-day window so we can spot real trends.
Total stars—
Total forks—
Total watchers—
Views (14d)—
Clones (14d)—
Repos tracked—
Repos · GitHub traffic
Click a header to sort. Click a row to expand referrers and popular paths.
| Repo | ⭐ | 🍴 | 👁 | Views (14d) | Clones (14d) | Trend |
|---|---|---|---|---|---|---|
| Loading repository data… | ||||||
Per-repo detail
Sparklines grow as history accumulates (need a few days of snapshots).
Loading…
Hosted sites · Microsoft Clarity
Engagement signals from the live Pages sites. Clarity captures sessions, scroll depth, dead clicks, rage clicks, and JS errors that the GitHub API can't see.
Loading…
How this works
- Source: a GitHub Action (
.github/workflows/traffic-snapshot.yml) runs nightly at 03:00 UTC. - Repos: queries
/repos/{owner}/{repo}/traffic/{views,clones,popular/referrers,popular/paths}for each tool. Daily view/clone buckets (the API returns up to 14 days per call, with overlap between runs) are merged into a year-to-date map keyed by date. Requires a PAT withreposcope, SSO-authorized for the microsoft org. Repos the token can't reach fall back to public meta only. - Sites: calls the Microsoft Clarity Data Export API per project (one token per project, capped at 10 calls/day each).
- Storage: appends to
docs/data/traffic-history.json, committed back tomainby the bot. Idempotent — re-running on the same day overwrites that day's data rather than appending duplicates. - Why it exists: GitHub's traffic API only retains 14 days. Clarity sees Pages traffic that GitHub can't. This page is the long-memory layer.