gh-dashboard logo

gh-dashboard

Open-source Git dashboard built for GIthub and Forgejo on REST and GraphQL APIs: repositories, issues, pull requests, traffic, Actions, contributors, dependents, and a kanban board view.

Developer ToolsAPI FrameworksTypeScriptMIT 359 42Health 77
discord
GitHub

What is it?

What it is

Gitdeck is an open‑source, local dashboard that lets users explore repositories, issues, pull requests, traffic, CI activity, and security alerts across multiple GitHub or Forgejo accounts from a single interface.

Why it exists

It was created to give developers a unified, offline‑ready view of many projects, providing insights, alerts, and daily digests that would otherwise require juggling multiple web pages or tools.

Who should use it

DevelopersDevOps engineersProject managers monitoring multiple repositories

Who should avoid it

Non-technical usersUsers without GitHub OAuth setup

How it works

A quick walkthrough in plain English

How gitdeck works

Step 1 of 3

You interact with it

Open gitdeck, send a request, or connect it to your stack.

Features

Centralized dashboard for GitHub and Forgejo-compatible repositories
Repositories grid with filters (language, stars, issues) and sorting options
Cross-repo issues and pull request lists for triage
Insights view with repo status alerts and traffic/activity correlations
Daily digest with AI-generated summaries (requires OpenAI API key)
Kanban-style board for issue management
Security alerts for Dependabot and code scanning findings
Per-repository deep dive with security, traffic, and contributor data
Local operation with no cloud dependency
OAuth Device Flow authentication for secure GitHub access

Advantages

  • Unified interface for managing multiple accounts and repositories
  • Local storage of tokens and data enhances privacy and security
  • AI-powered daily summaries improve productivity
  • Kanban board supports agile project management
  • Supports both GitHub and self-hosted forges (Codeberg, etc.)
  • No client secret required in OAuth Device Flow
  • Customizable filters and sorting for efficient repository management
  • Security alerts enable proactive issue resolution

Disadvantages

  • Requires GitHub OAuth App setup with Device Flow
  • AI digest feature depends on OpenAI API key availability
  • Early-stage project with potential for breaking changes
  • Limited topic filtering in repository views
  • No built-in support for non-English translations (requires manual setup)
  • Dependent on GitHub API availability and rate limits
  • Initial setup may be complex for non-technical users

Installation

docker

docker build -t gitdeck . && docker run -d --name gitdeck -p 8765:8765 -e GITHUB_CLIENT_ID=Iv1.xxxxxxxxxxxxxxxx -e OPENAI_API_KEY=sk-... -v gitdeck-data:/home/node/.gitdeck gitdeck

native

npm install && npm run dev

compose

cat > .env <<'EOF'
GITHUB_CLIENT_ID=Iv1.xxxxxxxxxxxxxxxx
# Optional — enables AI-generated daily digest narratives
OPENAI_API_KEY=sk-...
EOF

docker compose up -d --build

FAQ

What is Gitdeck and what can I do with it?

Gitdeck is a local, open‑source dashboard that lets you explore multiple GitHub or Forgejo repositories from a single interface. It shows repositories, issues, PRs, traffic, CI runs, security alerts, and daily digests, and offers filtering, sorting, and a Kanban board view.

How do I set up the GitHub OAuth Device Flow for authentication?

Create a GitHub OAuth App, enable Device Flow, copy the Client ID, export it as GITHUB_CLIENT_ID, then start the server. The first time you open the UI it will walk you through the Device Flow: GitHub will provide a user code and URL, you approve it, and the server stores the token locally.

What authentication modes are supported by Gitdeck?

Gitdeck can obtain a GitHub token via three modes: (1) device (default) – OAuth App + Device Flow; (2) gh‑cli – reads the token from the local GitHub CLI; (3) token – uses a personal access token set in GITHUB_TOKEN. Set GH_AUTH_MODE to choose.

How do I run Gitdeck locally in development?

Run `npm install` to install dependencies, then `npm run dev` to start both the API server and the Vite dev server. Open http://127.0.0.1:5173 and complete the sign‑in flow if needed.

Can I run Gitdeck in Docker?

Yes. Use the provided docker‑compose file: create a .env with GITHUB_CLIENT_ID (and optionally OPENAI_API_KEY), then run `docker compose up -d --build`. The container mounts a volume at /home/node/.gitdeck to persist tokens and data.

Loading documentation…
View on GitHub

Featured in Videos

YouTube tutorials and walkthroughs for gh-dashboard

Alternatives

Similar projects ranked by category, topics, and text overlap.

Compare
gh-dashboard | MushyBook