---
title: "Discussion on \"How we score the impact of an API change from 0 to 100\" | Hashnode"
description: "Discussion on \"How we score the impact of an API change from 0 to 100\". Four public rules with caps, three bands and a worked example: the arithmetic behind Graphwake's impact score, so you can check it."
url: "https://hashnode.com/posts/how-we-score-the-impact-of-an-api-change-from-0-to-100/6af8b0657c1e0edff3316b66"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [How we score the impact of an API change from 0 to 100](https://graphwake.hashnode.dev/how-we-score-the-impact-of-an-api-change-from-0-to-100?utm_source=hashnode&utm_medium=feed)

Four public rules with caps, three bands and a worked example: the arithmetic behind Graphwake's impact score, so you can check it.

1d ago · 3 min read · graphwake.hashnode.dev  
Read the article

-   [#apis](https://hashnode.com/tag/apis)
-   [#openapi](https://hashnode.com/tag/openapi)
-   [#devops](https://hashnode.com/tag/devops)
-   [#code-review](https://hashnode.com/tag/code-review)

## Written by

[Graphwake](https://hashnode.com/@graphwake)

@graphwake · Vancouver, Canada

  
[View profile](https://hashnode.com/@graphwake)

Founder of Graphwake. API changes between teams.

## Responses

Markdown supported · ⌘↵ to post

No responses yet.
