How it works

How the 0-100 impact score is built

Last checked 2026-11-022 min read

Every change set gets a score from 0 to 100 made of four parts, each with a cap. The rules are fixed and shown with every score, so you can check the arithmetic rather than trust a number.

ExamplePull request #1284 · orders-api · not merged
79/100Highbefore the merge
3 breaking changes
10 each, up to 30
30
3 consumer teams affected
12 each, up to 36
36
13 people notified
1 each, up to 14
13
Blind spots
10 each, up to 20
0
Low0-29Medium30-59High60+
Four public rules add up to the score, so a reviewer can check every point of it.
On this page
  1. The four parts
  2. The bands
  3. A worked example
  4. Why a blind spot counts
  5. What the score is for
  6. Questions

The four parts

PartCountsPoints eachCap
Breaking changesBreaking changes in the change set1030
Affected teamsConsumer teams subscribed to an endpoint with a breaking change1236
People to notifyDistinct people in those teams114
Blind spotsRemoved endpoints, and breaking changes on endpoints nobody subscribes to1020
See who your next breaking change reaches.Paste a spec URL or add one CI step. 7-day free trial. Cancel before day 7 and you pay nothing.
Start free trial

The caps add up to 100. Each part scores the lower of its count times its points, and its cap.

  • Public rules

    The rules are fixed and shown with every score, so you can check the arithmetic.

  • Informs, never blocks

    It helps reviewers decide where to look first. Graphwake never fails or blocks a build.

The bands

ScoreLevel
0-29Low
30-59Medium
60-100High

A change set with no breaking change scores 0: nothing breaks.

A worked example

Hypothetical example: a change set removes one response field and adds a required parameter on another endpoint. That is 2 breaking changes (20 points). Three teams subscribe to the affected endpoints (36 points, which is the cap), and together they have 9 people (9 points). One of the two endpoints has no subscribers: 1 blind spot (10 points). The score is 20 + 36 + 9 + 10 = 75, which is High.

Why a blind spot counts

A removed endpoint, or a breaking change on an endpoint with no subscribers, is a change whose reach is unknown. Counting it as risk pushes the team to find out who is affected before merging. Discovery suggests likely teams, with the reason for each suggestion.

What the score is for

It helps reviewers decide where to look first and who to talk to. With the CI step, reviewers see it while the change is still a pull request.

Questions

What is a good impact score?

Low (0-29) means few or no teams are affected. High (60 and above) means several breaking changes, several teams or blind spots.

Can I see why a change scored what it did?

Yes. Each score is shown with its four parts and the arithmetic.

Pick an endpoint. See who it reaches. 7-day free trial. Cancel before day 7 and you pay nothing.

Start free trial