/slashscore

methodology.

Every score is computed from public data by one published formula: percentiles all the way down, no hand-tuned caps, no opaque model. This page renders directly from the same formula definition the scoring engine executes, so what you read here is what runs.

formula v0 · decided 2026-07-15source: src/lib/formula/v0.ts

the four steps

  1. 1metric percentiles

    Every raw metric becomes its percentile rank over the entire pool, claimed and unclaimed alike: the share of the pool with a smaller value, ties counting half.

  2. 2dimension scores

    Each dimension is the plain average of its metric percentiles.

  3. 3source sub-scores

    A source’s sub-score is the weighted sum of its dimension scores, using the published weights below.

  4. 4headline

    Sub-scores are sorted descending, weighted 1, ½, ¼, …, and summed into a composite; the headline 0–100 is the composite’s percentile rank over the whole pool.

the formula, drawn

Line thickness is the weight. This diagram is generated from the formula definition, so when the formula changes, it redraws itself.

commitslast 12 monthspull requests mergedinto others’ reposlast 12 monthsstars acrossowned reposfollowerscode reviews onothers’ pull requestslast 12 monthsactive weeksof the last 52output40%adoption25%consistency20%influence15%githubsub-scoreΣ weighted dimscompositerank-decay Σ0–100percentile

worked example

Every number below is computed by the same engine that scores real profiles, so you can check the arithmetic yourself.

a hypothetical developer, pushed through the engine · percentiles against the live index (10,001 developers, refreshed daily)
412commits→ percentile0.79
9pull requests merged into others’ repos→ percentile0.78
mean → output0.79× weight0.40=0.31
120stars across owned repos→ percentile0.67
adoption0.67× weight0.25=0.17
41active weeks→ percentile0.61
consistency0.61× weight0.20=0.12
95followers→ percentile0.60
27code reviews on others’ pull requests→ percentile0.88
mean → influence0.74× weight0.15=0.11
Σ =0.72github sub-score → composite0.72→ percentile over the pool →81/100

github · dimensions & metrics

dimensionweightmetrics
output
code shipped, and accepted by others
40%
commits · last 12 months
pull requests merged into others’ repos · last 12 months
adoption
others building on your work
25%
stars across owned repos
consistency
showing up week after week
20%
active weeks · of the last 52
influence
reach and trust in the community
15%
followers
code reviews on others’ pull requests · last 12 months

versioning

Formula versions are frozen: recalibrating anything (weights, metrics, scales) is a new version, and every score snapshot records the version that produced it. History is never silently rewritten.

Seeded profiles carry provisional scores until their first real computation; claiming a profile computes it from live data immediately.

Wondering what the number means for you rather than how it is built? Why your score moved, whether it can be gamed, what is stored about you? The FAQ answers those in plain language.

/slashscore · public data only · no email, no tracking · privacy