Back to Home

GitPulse Scoring

How we measure developer output, without revealing the exact formula.

How GitPulse Works

GitPulse measures your developer output based on your recent GitHub activity. We combine multiple signals into a single score (0-100) that reflects how actively and consistently you ship code or maintain projects.

Two paths: You can reach high scores either by shipping code (commits) or by maintaining projects (reviews, PRs, issues). Your best path counts: pure shippers and pure maintainers can both reach elite levels.

Quality over quantity: Not all activity is weighted equally. We consider repo type, content, and consistency. Automated or low-quality contributions are filtered out. Spam and gaming attempts are detected and capped.

Recent activity only: We focus on the last 12 months. Sustained output over time matters more than short bursts.

What We Look At

Shipping: Commits in your repositories. We analyze where and what you ship. Real engineering work counts more than content-only or tutorial repos.

Maintenance: PR reviews, merged PRs, releases, and issue activity. Maintainers who keep projects moving get full credit.

Consistency & breadth: Regular activity across multiple projects is valued. One-off spikes matter less than steady contribution.

Weekly Ranking Points

The weekly leaderboard uses Ranking Points to rank makers each week. The period runs from Monday 00:00 UTC to Sunday 23:59 UTC.

The calendar week always counts in full: even if you sign up on Saturday, you still receive points for all activity from Monday through Saturday.

Shipper: Merged pull requests earn points based on quality signals (default branch, reviewers, linked issues). Solo commits on the default branch also count, with caps and diminishing returns to keep scoring fair for both solo founders and team developers.

Maintainer: PR reviews, approvals, merging others' PRs, and closing issues you didn't create all contribute. Maintainer activity is valued but does not dominate shipping.

Anti-spam: Only the default branch counts. Merge commits and bot commits are excluded. Daily caps prevent gaming through volume alone.

Anti-Gaming

We do not publish the exact scoring formula, weights, or thresholds. This is intentional: it helps keep the score meaningful and reduces manipulation. Automated commits, bot activity, and low-quality contributions are filtered or capped.

Score Labels

Your final score maps to a label that reflects your output level. Labels describe activity, not job titles.

Score RangeLabel
95-100Exceptional Output
85-94High Output
70-84Strong Output
55-69Active Contributor
35-54Consistent Contributor
15-34Occasional Contributor
0-14Limited Activity