HOW THE BOUNTY IS SET

DATA

Only public GitHub data. Profiles: account age, followers, original (non-fork) repositories, stars, forks, languages, README/license hygiene, recent pushes. With a server token we also read the last year of commits, pull requests, issues, reviews and weekly consistency. Repositories: stars, forks, watchers, contributors, releases, languages, age, license, last push.

SCORING

Each signal passes through diminishing returns, 1 − e^(−x/k), so quantity can't buy a bounty. Signals fold into five categories, then into one 0–100 score:

ACTIVITY
20%
IMPACT
30%
ENGINEERING
15%
COMMUNITY
20%
CONSISTENCY
15%

Anti-spam: hundreds of repositories with almost no stars get their activity discounted. Weights live in lib/scoring.ts.

BOUNTY

bounty = 1,000,000 × 10^(0.035 × score). Every score point multiplies the bounty by about 1.08, like real bounties escalate.

score 0	฿ 1,000,000
score 20	฿ 5,012,000
score 40	฿ 25,119,000
score 60	฿ 125,893,000
score 80	฿ 630,957,000
score 100	฿ 3,162,278,000

UNKNOWN≥ 0Barely a whisper on the open-source seas.

ROOKIE≥ 12A fresh name starting to appear on harbor boards.

DECKHAND≥ 25Reliable hands, steady contributions.

RAIDER≥ 40A known troublemaker with real commits behind it.

CAPTAIN≥ 55Leads crews and ships serious work.

SUPERNOVA≥ 70An unusually dangerous presence in the open-source seas.

YONKO≥ 85Rules entire waters of the ecosystem.

LEGENDARY≥ 95Spoken of in every port.

Classes are part of a game. They do not measure programming ability.

POSTER

The poster is drawn in code as SVG — never by an image model — so every letter stays sharp. Downloads are 1600×2240 PNG (or SVG) of exactly what you see, with fonts embedded.