# graphql-hive/graphql-inspector

🕵️‍♀️ Validate schema, get schema change notifications, validate operations, find breaking changes, look for similar types, schema coverage

Repository: https://github.com/graphql-hive/graphql-inspector
Canonical: https://ross.abutalabs.com/products/graphql-inspector
Homepage: https://the-guild.dev/graphql/inspector
Language: TypeScript
License: MIT
License Family: permissive
Topics: graphql, typescript, javascript, api, monitoring, probot-app, the-guild
Last push: 2026-08-20T14:06:31+00:00

## Health v2 (maintenance only)
Score: 98/100 (v2, computed 2026-09-03T02:20:16.233290+00:00)
- activity 98, release rhythm 98, longevity 100
- inputs: {"age_days": 2848, "days_push": 13, "days_rel": 13, "gap_med": 14.0, "n_releases_24m": 17}
- flags: none
- formula: round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10)

## Adoption (not part of the score)
Stars 1760, forks 216 (observed 2026-08-28T04:05:32.551005+00:00)

## What it is
GraphQL Inspector is a suite of tools for validating and monitoring GraphQL schemas. It diffs two schemas to flag breaking, dangerous, or non-breaking changes, validates operations against schemas, and reports schema coverage, available as a CLI, GitHub App/Action, and programmatic API.

## Use cases
- detect breaking changes in graphql schema between commits
- validate graphql operations against a schema in ci
- get slack notifications when graphql schema changes
- find duplicate or similar types in a graphql schema
- generate schema coverage reports from client operations
- review graphql schema changes on pull requests
- introspect a graphql api and save the schema
- serve a graphql server with mocked data

## When to choose
- you maintain a graphql api and want to prevent breaking changes via ci/cd
- you need schema change notifications on slack, discord, or webhooks
- you want automated graphql schema reviews on github pull requests
- you need to validate client documents and fragments against a schema
- you want to measure how much of your schema is actually used

## When to avoid
- you need full api performance monitoring and usage analytics - consider GraphQL Hive instead
- your project does not use graphql
- you need runtime api gateway or traffic management rather than schema tooling

## Facets
- artifact type: cli-tool
- maturity: stable
- function: graphql, developer-tools, testing, ci-cd, monitoring, api-framework
- domain: developer-tools, apis, web-development, testing
- platform: cli
- tags: graphql-schema, schema-diff, breaking-changes, github-action, github-app, schema-coverage, schema-registry, code-review, devops, nodejs, docker, web-server

## Member repositories
- graphql-hive/graphql-inspector (main) score 98

## Provenance
- Observed fields: from GitHub, fetched 2026-08-28T04:05:32.551005+00:00.
- Health v2: computed from the inputs above; adoption is never an input.
- Inferred fields (summary, facets, guidance): AI-extracted, prompt v1, taxonomy v1, on 2026-08-30T03:27:14.549607+00:00, confidence not recorded.
  - readme: https://github.com/graphql-hive/graphql-inspector (fetched 2026-08-28T04:05:32.551005+00:00, sha e2319cc0f84f)
  - homepage: https://the-guild.dev/graphql/inspector (fetched 2026-08-29T11:05:51.032124+00:00, sha dd74c00a01ff)
  - site_page: https://the-guild.dev/graphql/inspector/docs (fetched 2026-08-29T11:05:51.034638+00:00, sha 5fbc4802f84f)
  - site_page: https://the-guild.dev/about-us (fetched 2026-08-29T11:05:51.036520+00:00, sha 4c4f11519fb9)
- Data as of 2026-08-30T08:39:29.467469+00:00.