12 Oct – 18 Oct 2026 · UTC · in progress

Vaibhav Tanwar

@Vaibtan · New Delhi, India · on GitHub since 2021

← back to Vaibhav Tanwar

How this week scored

Private contributions, at a flat rate2 contributions × 4080

0 lines, credited on the curve · 2 private, at a flat rate → 80 credited, on the four-digit scale99

Consistency

1/7

active days. These do not score — nothing multiplies a week any more. Consistency is the ladder instead: a week is measured against what your rung expects, and a week missed costs rating that takes several good ones to win back.

Behind a closed door

contributions in private repositories over the last ninety days. That is real work in a real job, and it is the single largest thing a contribution graph gets wrong about a developer.

2 of them this week, counted at a flat 40 lines each — 80 credited lines. Connecting repositories counts the actual lines instead, with no ceiling.

Week rhythm · hour of week, UTC

MONTUEWEDTHUFRISATSUN

Score by week · last 13

2026-07-20this week

What you are looking at

A weekly rank, scored on work that took someone else’s approval.

Not contribution count. Lines you wrote, credited on a curve so one enormous drop cannot buy a week, plus a share of the lines you reviewed for other people — which is why the top of a table is often somebody who wrote very little code and read a great deal of it.

Every score is ranked against a real crowd — the percentile above says which one and how many people are in it — and it is recomputed every day. Leagues settle on Monday.

Get your own rank every weight and every exclusion ->

read-only · you pick the repositories · we never write anything