See how your team really builds software.

Sample data. A screenshot of a real run would show real people's working hours.

Drawn, not screenshotted, and every number invented. A screenshot of a real run would show real people's logins and the hours they work.

highlights

Up to six ranked observations for the person and period you pick, each set against the period before: after-hours climbing, weekends worked, the longest run without a day off, products only one person knows.

any-stretch-of-time

A year, the last 3 or 12 months, or any two dates down to the minute, narrowed if you like to a time of day such as 10 PM to 5 AM. Every chart, link and report follows it.

when-commits-happen

An hour-by-weekday grid, hourly and weekday charts, and a calendar of every single day. Office hours adjust in 15-minute steps; everyone can be converted to one timezone.

quarterly-delivery

A stacked chart by product and a quarter-by-product table, with repositories grouped into the products they belong to instead of listed as raw repo names.

code-frequency

Lines added and removed over time, and a card per contributor, modelled on GitHub's own graphs. Vendored and generated monsters are cut off and marked, not allowed to flatten the chart.

pull-requests

Opened and merged, median time to merge, share merged within a day, the distribution, and the pull requests that have been waiting longest. Drafts do not count as waiting.

team-comparison

Share of commits, pull requests, merges, reviews and issues, a leaderboard for the period you pick, and after-hours numbers per person - with two accounts belonging to one person merged. Click anyone's share or count for the commits, pull requests and issues behind it.

commits-behind-it

Click any mark - a day, an hour, a quarter cell - to list the commits and pull requests behind it, what each says and a link to it on GitHub. Narrow it by period, time of day, repository or person without leaving it, or drag across its timeline. Copy it as Markdown for a stand-up or an appraisal.

ai-tools

What Claude Code and Codex did on this computer, from the logs they keep here: tokens, requests and prompts on the same calendar and hour-by-weekday grid as your commits, ranked by model, folder and tool. Numbers only, never what was typed.

notifications

A pull request waiting on your review, one of yours left open three days, a weekly recap, a sync that failed: in the app, and from the system while the app is open. Never from a background process.

Each highlight is measured against the period before it, so the page tells you what changed rather than what is merely large.

network

api.github.com, with your own token - and one other request, below

updates

at most every six hours it fetches latest.json from assets.gitdashx.com to see whether a newer version is out: a public file, asked for with nothing about you or your data in it. The Windows installer and the AppImage then download the new build from there too. Turn it off under the account menu, or with GTS_NO_UPDATE_CHECK=1

server

none - the app runs one on 127.0.0.1 for itself

account

none to create

telemetry

none

source code

never downloaded: git clone --mirror --filter=tree:0 fetches commit metadata and skips file contents

AI tool logs

read, never written: the logs Claude Code and Codex keep on this computer, for the AI tab. It keeps their counts, model and tool names, folders and session titles, never what was typed or said

token

encrypted with the OS keystore (DPAPI on Windows), held by the app process, never handed to the page

listener

refuses requests whose Host is not localhost, cross-site requests by Origin, and non-JSON writes

your data

a folder on your machine; delete it and nothing of it survives elsewhere

Contribution analytics means reading how your colleagues spend their working hours. That is exactly the kind of data that should not be sitting on somebody else's server.

1. 01installChoose your build. Windows carries Git; macOS and Linux use the Git already installed on your computer. No Node or GitHub CLI needed. Or run the Docker image and open it in your browser.
2. 02connectA short code approved in your browser, a personal access token, or an account the GitHub CLI already holds.
3. 03selectTick the organizations you want, optionally your personal repositories, and press Analyze.
4. 04leave itThe first sync pulls history; later ones fetch only what is new, hourly, in the background while you read.

?

Does anything leave my computer?

Nothing about you or your data. It makes requests to GitHub's own API with your token, and at most every six hours fetches a public file from this site to see whether a newer version is out; that check can be turned off in the account menu. There is no GitDashx server, no account and no telemetry. Everything it works out is stored in a folder on your machine.

?

How does it update?

The Windows installer and the Linux AppImage download a new version in the background, then offer a restart; it also installs the next time you quit. The macOS builds, the portable Windows app and the .deb show that a new version is out, with a link to it. The Docker image shows the docker pull to run.

?

Does it download our source code?

No. It mirrors history with git clone --mirror --filter=tree:0, which fetches commit metadata and skips file contents entirely. It never reads what is inside your files.

?

What access does it ask for?

A GitHub token with the repo and read:org scopes. It reads commit metadata, pull requests and repository statistics, and never writes to your repositories.

?

Why does Windows warn me when I run it?

The Windows builds are not code-signed, so SmartScreen flags an unknown publisher. Choose More info, then Run anyway. Every release publishes a SHA-256 checksum you can verify first. With Smart App Control on, Windows blocks unsigned apps outright and there is no way past, so run the Docker image instead.

?

Why won't the AppImage open?

Mark it executable first: chmod +x, or Allow executing as program in its properties. It needs FUSE 2, which Ubuntu 22.04 and later leave out: install libfuse2 (libfuse2t64 on 24.04). On Ubuntu 24.04 and later AppArmor also stops its sandbox. The .deb has neither problem. Or run the Docker image.

?

Why does macOS warn me when I open it?

This Mac build uses ad-hoc signing for testing and is not notarized by Apple. After checking its SHA-256, allow it from Privacy & Security in System Settings. Or skip the app and run the Docker image.

?

Can I run it with Docker?

Yes: docker run -d --name gitdashx -p 127.0.0.1:8787:8787 -v gitdashx:/data hicoders/gitdashx, then open http://localhost:8787. It is the same dashboard as the desktop app, built for Intel and ARM with Git included, and keeps its data in the gitdashx volume. Already signed in to the GitHub CLI? Add -e GH_TOKEN=$(gh auth token) to skip the sign-in screen. Keep the 127.0.0.1 in the command: the dashboard has no login of its own.

?

Do I need Git or the GitHub CLI installed?

Windows carries its own copy of Git. The macOS and Linux builds use Git installed on your computer. GitHub CLI is optional on every platform; when it is installed and signed in, the app offers those accounts as a shortcut.

?

Which desktop platforms are available?

The current release publishes downloads for Windows, macOS, Linux. Only builds listed on this page are available.