v0.1.0 · git-native · zero telemetry

Repository metrics without the drag.

Track lines of code, ownership, history, and churn across git repositories without slow indexing or heavyweight setup.

Install codeye Download binaries
Single static Go binary Tracked files only JSON, CSV, Markdown, badge
$ go install github.com/blu3ph4ntom/codeye/cmd/codeye@latest
~/src/service-api
❯ codeye --format table --sort code
codeye · main · 62 files · 55ms
Language Files Code Comments Blanks Total %
▌ Go 31 4,247 415 500 5,162 66.3%
▌ Markdown 8 670 0 209 879 11.3%
▌ CSS 1 526 16 17 559 7.2%
▌ YAML 4 305 1 48 354 4.5%
Total 62 6,414 467 900 7,781 100.0%
✓ cache-aware · tracked files only · no daemon

❯ codeye --blame --top 3
running blame (may take a moment)...
alice@example.com 5,591 89.1% ██████████████████████████████████
bob@example.com 685 10.9% ████
Diff and history aware Scan HEAD, a branch, a commit, or compare two refs.
Built for automation Stable JSON, NDJSON, CSV, Markdown, compact, and badge outputs.
Safe to drop into CI No CGO, no background service, no language-specific runtime required.
Why teams use it

Fast enough for local loops, structured enough for pipelines.

codeye stays opinionated about one thing: repository insight should be immediate, scriptable, and boring to operate.

01

Language composition

Count code, comment, and blank lines by language with git-aware file selection and low-overhead repeat scans.

02

Ownership snapshots

Use blame rollups to see who owns the codebase surface area before changes, reviews, or maintenance work.

03

Trend visibility

Track repository growth over time and spot the files that churn hardest relative to their size.

04

Ref-to-ref diffs

Compare tags, branches, or arbitrary commits when you need release-level deltas instead of one current-state snapshot.

05

Works with real repos

Respects tracked files and `.codeyeignore`, with a fallback directory scan when the target is not a git repo.

06

One binary, many outputs

Use the default terminal view locally, then switch to JSON, CSV, Markdown, or badges without a second toolchain.

Typical flows

Useful on day one.

CLI checks in CI

Export JSON or badge output during pull requests and releases to keep repository metrics visible without custom parsing.

Maintenance triage

Pair `--hotspots` with `--history` to identify unstable files and the code that keeps absorbing changes.

Audit and ownership

Use `--blame` before refactors or handoffs to get a quick ownership distribution across the repo.

Quick commands
# Current repo snapshot
$ codeye .

# Compare releases
$ codeye diff v0.1.0 HEAD

# Ownership summary
$ codeye --blame --top 10

# CI-friendly output
$ codeye --format json .
Open full usage reference
Install

Choose the path that fits your environment.

Start with `go install`, use the release archives for pinned binaries, or host the install scripts directly from GitHub Pages.

Go install

$ go install github.com/blu3ph4ntom/codeye/cmd/codeye@latest

POSIX installer

$ curl -sSfL https://codeye.bluephantom.dev/install.sh | sh

Windows installer

iex (irm https://codeye.bluephantom.dev/install.ps1)

Ship repository insight with less ceremony.

Browse the docs, download a release, or wire the Pages site into your custom domain.

Read the docs View source