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. Reviewing is how the work gets in, so a pull request someone else wrote counts for each person who reviewed it: once, however many rounds or comments the review took. A commit counts, but a commit on its own is not a contribution. The weights below are the ones the server scores with, read from it as this page is built.

score = merged pull requests   × 10
      + pull requests reviewed × 8
      + commits                × 1
      + issues opened          × 0.5

Rules version 2, since 23 September 2026: a review counts once per pull request reviewed. Until then, every review submission counted on its own, so feedback split into several replies counted several times. A reviewed pull request now weighs more, and another reply on it adds nothing: people who review many pull requests moved up, and a long thread on one pull request now counts once. The ladder’s thresholds did not change.

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. The repositories synced are La Suite numérique’s own, under the suitenumerique organization, Tchap’s and Grist’s, and Element’s for the people attributed to the ecosystem’s organizations only; 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.

Comments on other people’s pull requests and issues are shown beside a contributor’s score as discussion, and never counted in it: a comment is too easy to multiply to rank anyone by. Replies in a review’s threads are part of the review; the text of a comment is never stored.

A contributor is attributed to an organization from four sources, the higher one winning: a steward of that organization adding them; the curated list in server/config/organizations.yaml; a claim they make themselves after signing in, once it is verified by their membership of the organization on GitHub or by one of its stewards or a Reportz maintainer; and the company field on their public GitHub profile. A person belongs to one organization only; a profile that names two is left unattributed until another source settles it.

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 join your organization, sign in and claim it. To correct an attribution or add someone else, write to us at support@samourai.coop: the curated 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 support@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, stores nothing of yours, and removes your commits, pull requests, issues, reviews, comments 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.