Get access
How it works

Your score, in plain terms

code.live turns public GitHub work into a single 0–1000 score. Seven pillars. One formula. Three guardrails. Methodology stays versioned so results stay explainable.

Overall formula

score = Σ (pillar_score × weight × 1000)

Each pillar_score is 0–1. Weights sum to 1.0. Result is 0–1000.

Score bands

Where you land on the 0–1000 scale.

  • Elite
    800–1000
  • Strong
    600–799
  • Competent
    300–599
  • Developing
    0–299

Hiring verdict

Thresholds on your profile. Quality pillar has a separate minimum.

  • Strong Hire
    ≥ 750Quality ≥ 60%
  • Hireable
    ≥ 650Quality ≥ 50%
  • Needs Review
    ≥ 500Quality —
  • Not Ready
    < 500Quality —

Minimum hireable score is 650 with Quality pillar ≥ 50%. Below 500 = Not Ready.

Seven pillars

Each is scored 0–1, then scaled by its weight.

  • 01
    Activity15%

    Commits, PRs, and issues over rolling 30/90/365-day windows.

  • 02
    Collaboration15%

    Merged PRs, reviews, external contributions, and issue participation.

  • 03
    Impact20%

    Stars, forks, followers, and OSS adoption on repos you touch.

  • 04
    Quality20%

    README depth, structure, docs ratio, complexity, tests, and CI.

  • 05
    Consistency10%

    Active-day ratio, longest streak, and commit evenness over 12 months.

  • 06
    Experience10%

    Account age — log-scaled so early years matter more than later ones.

  • 07
    Builder10%

    Owned repos, starred projects, average quality at scale, and maintenance.

Guardrails

Applied after the weighted sum. Prevent gaming and outlier inflation.

  • G1Quality floor

    Trigger: Quality pillar < 40%

    Effect: Capped at Needs Review — blocks Hireable / Strong Hire regardless of total score.

  • G2Spike penalty

    Trigger: Activity > 75% but Consistency < 35%

    Effect: Score × 0.95 (−5%). Spikes don't count the same as sustained output.

  • G3Viral dampener

    Trigger: Single repo > 90% of total stars AND score 650–700

    Effect: Score × 0.97 (−3%). One hit ≠ a body of work.

Data: read-only access to public activity — no private repos, no source code stored, only aggregated metrics.

Leaderboard: you opt in and must clear a confidence threshold before appearing publicly.

FAQ

How is the developer score calculated?
Public GitHub signals are grouped into seven pillars (activity, collaboration, impact, quality, consistency, experience, builder). Each is normalized and scaled to 0–1, multiplied by its weight, then summed into a 0–1000 score. Guardrails apply post-computation to prevent gaming.
What is the minimum score to be hireable?
650 out of 1000 — and the Quality pillar must score at least 50%. A high total score with low quality gets guardrailed down to Needs Review.
How often does my score update?
Scores refresh incrementally after new public activity, with at least a daily full pass. Re-scores can use stored metrics without re-fetching your entire history.
What about gaming and trust?
Three built-in guardrails dampen obvious patterns: a quality floor blocks low-craft profiles, a spike penalty punishes burst-then-silent patterns, and a viral dampener prevents one lucky repo from inflating the overall. A confidence score is shown next to every headline number.
What data do you access?
Read-only access to public activity — no private repos, no source code stored, only aggregated metrics. Disconnect or request deletion anytime.

Ready to see numbers? Join the waitlist or browse the leaderboard.