How the numbers are made.

A contributor’s score is a weighted sum of what they shipped in the window you are looking at. A merged pull request is the unit of work. A review is worth half of one, because reviewing is how the work gets in. A commit counts, but a commit on its own is not a contribution.

score = merged pull requests × 10
      + reviews              × 5
      + commits              × 1
      + issues opened        × 0.5

These weights replaced the ones inherited from Gnolove, the project this site was forked from, under which a single commit outweighed five merged pull requests and a three-pull-request contributor could outrank a seventeen-pull-request one.

A contributor’s status is read off their 30-day score: ten tiers, named for the way work moves through a repository. It is a moving state, not a medal: it describes the last thirty days and changes as they do. A window with nothing in it shows no status at all. The ten names stay in English: they are the words of the work itself, and the ones the badges and share images carry.

01  signal      score > 0
02  patch       score ≥ 10
03  commit      score ≥ 30
04  branch      score ≥ 60
05  merge       score ≥ 100
06  pipeline    score ≥ 160
07  builder     score ≥ 250
08  maintainer  score ≥ 380
09  core        score ≥ 550
10  kernel      score ≥ 800

The thresholds are constants in the repository and change only by pull request, the same rule as the weights above, because a rank people carry deserves published rules.

Only merged pull requests count: an open one is not work delivered. Bots are excluded from pull-request authorship. Thirteen repositories under the suitenumerique organization are synced; the list lives in server/config/ecosystem-config.yaml and changes by pull request.

Bots are excluded everywhere: pull-request and review authors at the GitHub type level, commits by GitHub Apps at ingest, and machine accounts that look like ordinary users against server/config/bots.yaml, a short published list that changes by pull request.

A contributor is attributed to an organization in one of two ways: a curated list in server/config/organizations.yaml, or the company field on their public GitHub profile. Curated entries win over the profile field.

Commit e-mail addresses are never used to infer an employer. It would work, and it would be a betrayal of everyone who ever pushed from a work laptop.

To claim an organization, correct an attribution, or add a member, write to us at hello@samourai.coop. The list lives in a file in the repository, which is not public yet, so we make the change ourselves and tell you when it is live.

If you would rather not appear here, write to hello@samourai.coop and ask to be taken off. No justification required, and no follow-up questions. Adding you to the list is a person’s job, so allow a day or two; after that it is automatic and permanent. Every sync checks the list and removes your commits, pull requests, issues, reviews and attribution again, so nothing can quietly put you back. The list itself is never published.

Avatars and organization logos are served through this site’s own image proxy: your browser never talks to GitHub or any other third party when someone views a board or an embed. Where no image exists, a monogram is generated locally from the name.