gitledger

Your Git history is your work ledger.

GitLedger automatically tracks the work you do in local Git repositories — commits, branches, pushes, lines changed — and visualizes it at gitledger.cvasingh.com.

Privacy first: GitLedger never uploads source code. Only Git metadata (commit hashes, messages, line counts, timestamps) ever leaves your machine — no file contents, no file names, no diffs. Verify it yourself: gitledger privacy inspect shows the exact bytes queued for transmission.

Quick start

npm install -g gitledger

gitledger login          # approve this machine in your browser  (alias: gl)
gitledger init           # start tracking a repository (auto-detects everything)
gitledger sync           # backfill history + upload
gitledger watch --daemon # sync automatically as you work

Commands

| Command | Description | | ------------------ | ------------------------------------------------------------- | | login | Device-code authentication with your dashboard | | init / add | Track repositories (identity, remote, language auto-detected) | | remove / list | Manage tracked repositories | | sync | Extract new activity and force-upload (--backfill <days>) | | status | Queue depth, API connectivity, per-repo state | | watch | Auto-sync daemon (--daemon / --stop) | | queue <action> | stats · inspect-dead · retry-dead · purge-dead | | privacy [action] | show · inspect · audit · export — audit what is sent | | doctor | Diagnostics with actionable fixes |

How it works

• Watches only .git internals (never your working tree) with a 2s debounce.
• Events queue locally (AES-256-GCM encrypted), then upload in batches with retry, exponential backoff, and a dead-letter queue — offline-safe by design.
• The server deduplicates by commit hash, so retries and multi-machine setups never double-count.

MIT © Shiva Singh