Rank yourself
as a coder.

No. Not a line of it leaves your machine. What we receive is session records, event stream and commit metadata. What we never receive is your code, your prompts, file names, commit messages and transcripts. What goes but never as itself is commands, file paths, project id, author email and branch names — hashed on your machine, so even the names are gone before the upload is built.

That is a property of how the payload is constructed, not a promise about how we behave. Everything textual lives on a part of each event that the projection to the wire format does not copy. A second check then scans the finished payload for about thirty forbidden keys at any depth and refuses to send if it finds one — on your machine before the upload, and again on our server when it arrives.

No. Nothing goes to Claude, to GPT, or to any model — ours or anybody else's. There is no model provider in the product at all.

Your score is arithmetic: counts compared against fixed curves. Nothing reads your work to form an opinion of it, because nothing we hold contains your work.

Yes, and there is a command that does nothing else. builder analyze runs the whole pipeline locally — no network, no server, no account — and prints the evidence it found. You can see everything it would say about you with nothing leaving the machine.

builder publish then shows the exact counts it is about to send along with three real sample events, and stops to ask. That last question is the one --yes cannot answer. Prompts are read from the terminal directly rather than from standard input, so piping the installer into a shell cannot answer them for you either.

Yes, two ways. builder unlink takes this machine off your profile and keeps its evidence. builder forget deletes this machine's evidence and score outright — and if it was the last machine on the profile, the handle and any email address go with it.

A score you never claim deletes itself. Unclaimed uploads are hard-deleted after 30 days, swept daily, with nothing required from you.

Four: Claude Code, Cursor, opencode and Codex CLI. It reads the session history each one already keeps on your disk, plus git metadata for the repositories those sessions point at. Cursor's database is opened read-only and immutable; git is run without hooks and never with a diff.

Codex CLI is the exception: that reader is written from the documented file format and has never been run against real data. builder discover marks it unverified rather than quietly counting what it find.

That is Node missing, not this. npx ships with npm, which ships with Node, and PowerShell is telling you there is no such command on the machine — so nothing of ours ran at all. node -v confirms it in one line.

You do not need Node. In PowerShell: irm https://poachdev.com/install.ps1 | iex — it downloads the Windows build, checks its SHA-256 before running anything, and installs into your own user profile. If you would rather have Node anyway, winget install OpenJS.NodeJS.LTS, then open a NEW terminal so PATH is picked up, and npx rankmycode works.

Windows is x64 only. There is no ARM64 build, and both the installer and npx refuse that machine rather than handing it an x64 binary to emulate.

No. It is a single binary in ~/.local/bin, run from your shell. There is no container, no daemon and no background agent — when the command exits, nothing of ours is still running.

No. There is no sign-in, no password, no email and no GitHub connection. Your machine registers a device token the first time it publishes, and a recovery key is what carries that identity to a machine which does not have it yet.

A score stays anonymous until you decide otherwise. Putting your name on one means typing an eight-character code your terminal prints, good for ten minutes and usable once.

No. There is no payment path in the product — no plan, no quota, and nothing to enter a card into.

Reading is seconds. On the machine this was built on, 272 sessions and 110,343 events were collected in about six seconds.

Publishing takes as long as the upload does: a year of heavy use is roughly 8 MB compressed. Scoring happens on our side, and the command waits for it rather than leaving you to refresh a page.

Yes. Every project your sessions point at is collected and merged by repository, so a repo seen by two different tools counts once rather than twice. --all-repos additionally scans your home directory for git repositories with no sessions attached.

Each machine is its own device. Uploads replace per device rather than summing, and several devices can be claimed onto one profile.

builder restore puts the new machine onto a profile you already have. It asks for a recovery key rather than for your handle, because a handle is public and anybody could type yours.

builder key prints a fresh key from a machine already on the profile. Keep one somewhere that will outlive the disk it was generated on — a machine nobody can prove owns a profile is the one case this cannot fix for you.

Ranking needs a claimed profile and enough evidence to stand behind: 12 effective episodes' worth of work across 8 active days, at 0.65 confidence or better. Sessions are weighed rather than counted, so a handful of substantial ones go further than a pile of short ones.

Percentiles stay hidden until at least 100 people are ranked. A percentile with no population behind it is a made-up number.

With enough effort, yes — and we would rather say so than claim a guarantee we cannot keep. Your machine never states a number: it sends evidence, and the score is computed here. Forging one means forging a session history that holds together when we check it, which costs more than it returns and leaves marks we look for.

That is cost plus detection. It is not proof, and nothing on this site will tell you it is.

Not any more. The collector was mirrored publicly under MIT between 14 and 17 September 2026 and has been proprietary since. Making the repository private stops new copies; it does not revoke the grant on copies already taken, which is why this says so rather than leaving it to be found out.

The part that matters is still checkable without trusting us, because it runs on your hardware: https://poachdev.com/run.sh is served verbatim and is the same bytes the install command pipes into your shell, and the binary it fetches is verified against a published checksum before it is made executable.

Thin, and honest about it. The five dimensions are stable and measure what they say they measure. The thresholds behind them are calibrated against one person's history, plus two anchors taken from a published analysis of 6,852 Claude Code sessions.

Scores recompute from stored evidence rather than from whatever was true at upload time, so replacing those guesses with real percentiles as the population grows is a rescore on our side — never something you have to run again.