GitHub Traffic insights dashboard for shigechika repositories.
English | 日本語
Live dashboard: https://shigechika.github.io/github-insights/
Last updated: 2026-11-22T15:38:59Z
xychart-beta horizontal
title "Views by Repository (251 days)"
x-axis ["mcp-stdio", "jquants-mcp", "junos-ops", "gws-mcp", "github-insights", "junos-mcp", "keycloak-mcp", "aruba-central-mcp"]
y-axis "Views"
bar [2754, 2606, 1092, 768, 624, 523, 520, 418]
---
config:
xyChart:
height: 760
---
xychart-beta horizontal
title "Daily Views (Last 30 days)"
x-axis ["10-24", "10-25", "10-26", "10-27", "10-28", "10-29", "10-30", "10-31", "11-01", "11-02", "11-03", "11-04", "11-05", "11-06", "11-07", "11-08", "11-09", "11-10", "11-11", "11-12", "11-13", "11-14", "11-15", "11-16", "11-17", "11-18", "11-19", "11-20", "11-21", "11-22"]
y-axis "Views"
bar [36, 12, 57, 17, 288, 777, 165, 21, 33, 26, 21, 19, 1038, 10, 17, 22, 18, 17, 39, 13, 5, 7, 21, 15, 8, 8, 24, 21, 20, 0]
---
config:
xyChart:
height: 300
---
xychart-beta horizontal
title "Daily Ranking (Top 10 days by views)"
x-axis ["2026-11-05", "2026-10-29", "2026-05-08", "2026-10-28", "2026-07-24", "2026-07-12", "2026-05-07", "2026-08-11", "2026-04-04", "2026-05-03"]
y-axis "Views"
bar [1038, 777, 355, 288, 261, 249, 191, 189, 170, 168]
xychart-beta horizontal
title "Clones by Repository (251 days)"
x-axis ["jquants-mcp", "mcp-stdio", "keycloak-mcp", "github-insights", "gws-mcp", "junos-ops", "junos-mcp", "gwsadm-mcp"]
y-axis "Clones"
bar [27167, 24943, 8258, 6839, 6627, 5894, 5480, 5257]
| Repository | Description |
|---|---|
| jquants-mcp | MCP server for Japanese stock market data via J-Quants API — tools for price history, financials, screeners, and candlestick charts |
| mcp-stdio | Bidirectional stdio ↔ HTTP gateway for MCP servers — connect clients to remote servers or publish local servers |
| keycloak-mcp | MCP server for the Keycloak Admin REST API — a strong ally for auth troubleshooting: inspect users, sessions, clients, and realm config through AI assistants. |
| github-insights | GitHub Traffic insights dashboard — aggregates views/clones across a user's public repositories |
| gws-mcp | MCP fork of Google Workspace CLI — exposes Drive, Gmail, Calendar, Sheets, Docs, Chat, Admin, and more to AI assistants. Dynamically built from Google Discovery Service. Includes AI agent skills. |
| junos-ops | Python CLI to automate Juniper/JUNOS operations over NETCONF: model-aware upgrade, rollback, reboot, config push, and RSI/SCF collection |
| junos-mcp | MCP server for Juniper/JUNOS — show, upgrade with rollback, config push (commit confirmed) with safe dry-run defaults, RSI/SCF collection |
| gwsadm-mcp | MCP server for Google Workspace security auditing — login audit, external sharing, daily brief |
| aruba-central-mcp | MCP server for Aruba Central: expose AP, switch, and client status to AI assistants |
GitHub only retains traffic data (views & clones) for 14 days. github-insights leverages GitHub Actions and the GitHub ecosystem to collect data daily, preserve it long-term, and keep traffic insights automatically up to date.
- Interactive dashboard: Stacked area charts (views & clones) on GitHub Pages with 30d / 90d / 1y / All range toggles
- Cross-repository aggregation: Unified stats across all your public repositories
- Rename-aware: Detects repository renames via GitHub API's 301 redirect and merges history under the new name automatically
- Long-term retention: Preserves traffic data beyond GitHub's 14-day window
- Template-ready: One-click "Use this template" — the dashboard derives owner/repo from
window.location, so a fork self-configures with no code edits
- Daily collection: GitHub Actions runs
scripts/collect.shon a cron schedule - Data storage: Traffic snapshots are merged into
data/traffic.json, deduplicating by timestamp - Visualization: The dashboard at
docs/index.htmlfetchesdata/traffic.jsonfromraw.githubusercontent.comand renders stacked area charts with Chart.js
Click Use this template → Create a new repository at the top of this repo to spin up your own dashboard. After creating your copy:
-
Reset the data so the dashboard starts fresh for your account:
echo '{"updated_at":"","views":{},"clones":{}}' > data/traffic.json git commit -am "chore: reset traffic data" git push
-
Create a Fine-grained PAT at https://github.com/settings/personal-access-tokens/new:
- Token name: anything descriptive, e.g.
github-insights - Repository access: All repositories or Only select repositories (the Public repositories preset cannot grant the Administration permission required by the Traffic API)
- Permissions → Repository → Administration: Read-only
Note: Although "All repositories" grants access to your private repos as well, this tool targets public repositories only —
scripts/collect.shlists them withgh api users/<owner>/repos?type=public. The PAT is scoped to read-only via the Administration permission, keeping the required access to the minimum necessary.After creating the token, check its permissions page against this example screenshot.
- Token name: anything descriptive, e.g.
-
Add the token as a secret named
GH_INSIGHTS_PAT(Settings → Secrets and variables → Actions → New repository secret). -
Enable GitHub Pages at Settings → Pages:
- Source: Deploy from a branch
- Branch:
main/ Folder:/docs
-
Run the workflow once to seed data:
gh workflow run collect.yml
Wait a few minutes, then visit
https://<your-username>.github.io/<your-repo>/.
After that, the cron runs automatically. Two or three times a day is a good baseline — scheduled runs can occasionally be delayed or fail to trigger entirely, so multiple runs per day ensures data is reliably captured. Adjust the schedule in .github/workflows/collect.yml to suit your needs. Avoid scheduling at the top of the hour (especially 00:00 UTC) as runs can be delayed or fail to fire (GitHub Docs).
Troubleshooting: If the workflow fails with
gh: To use GitHub CLI in a GitHub Actions workflow, set the GH_TOKEN environment variable, theGH_INSIGHTS_PATsecret from step 3 above (using the PAT created in step 2) hasn't been added to this repo — or was added under a different name. Check Settings → Secrets and variables → Actions → Repository secrets.
MIT — Originally created by shigechika/github-insights
