How the githubworth estimate is made

A repo's code and its git history are counted in tokens and priced at the rates Pangea publishes: $100 per million tokens of code and $40 per million tokens of history, checked October 20, 2026. Each repo gets a figure, a range and a list of buyer checks.

The code is counted with the buyer's own rules

• Code files count in full.
• Docs, config and data files count up to 10 times the code beside them.
• Dependencies, builds, caches and minified files are left out, including any file with a single line of 100 KB or more.
• Four bytes make one token.

These are the rules in pre.dev's pricing script, which prices repos for Pangea. A username page counts up to 30 of the profile's public, original repos, the most-starred first, and says so when the count is partial.

The history is estimated from the commit count

Git history is every past version of every file, and it's most of a repo's value: at the median, 80% of it. A website can't read it, so we estimate it from two things GitHub reports, the code size and the number of commits, with a formula fitted on 477 public repos whose history we counted in full with pre.dev's script on October 20, 2026. The estimate was within 2× of the real count for 56% of those repos. The range on the page is where 8 in 10 of them landed: from 0.27 times the estimate to 3.8 times. A repo with 21 commits or fewer gets a low end with no history at all, because repos that small sometimes had none. Source vs history, explained.

If you run the script yourself, the history is counted, not estimated, and there is no range.

The buyer checks don't change the figure

Each repo is checked against what buyers publish as their criteria: private, not a fork, has source code, has history, 100 or more commits, a year or more of work, issues in use, a README, tests, CI, a Dockerfile or compose file, more than one contributor, and owned outright. Each check is met, failed or unknown, and the page says which. Two are always unknown for now: whether you own the code outright, which no API shows, and the contributor count, which we don't read yet. Whether a private repo was ever public, only you know. The checks are a count, not a grade. Pangea grades repos itself before it pays.

What the figure means

Pangea licenses private repos you own that were never public to AI labs, non-exclusively, so you keep the code. Public repos, forks, client work and employer code don't qualify. So the estimate on a username page is what that code would list for if it were private; it isn't an offer for public code. On the private repos page, it's the list price before Pangea grades your repos.

What we store

Your username, avatar link and public code count, and each counted repo's name, main language, stars, commits, issue count, creation and last-push dates, token count and which checks it met, for your page at /u/your-name, refreshed about hourly. Private repo counts are never stored. You can remove your page.