A toolkit for validating, comparing, and monitoring GraphQL schemas to detect breaking changes and ensure compatibility.
GraphQL Inspector is a toolkit for validating, comparing, and monitoring GraphQL schemas. It detects breaking changes between schema versions, validates operations against schemas, finds similar types, and measures schema coverage. It solves the problem of maintaining GraphQL API stability during evolution by providing automated checks and insights.
GraphQL API developers, backend engineers, and DevOps teams who need to manage schema changes, ensure backward compatibility, and integrate validation into CI/CD pipelines.
Developers choose GraphQL Inspector for its precise change detection, comprehensive validation features, and flexible integration options (CLI, GitHub Actions, programmatic API). It provides actionable feedback to prevent breaking changes and maintain API reliability.
🕵️♀️ Validate schema, get schema change notifications, validate operations, find breaking changes, look for similar types, schema coverage
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Outputs a detailed list of schema changes marked as breaking, non-breaking, or dangerous, enabling precise control over API evolution, as highlighted in the README's focus on actionable insights.
Available as CLI, GitHub Action, and programmatic API, making it easy to embed into various development and CI/CD workflows, as shown in the installation methods.
Includes operation validation, schema coverage analysis, and a fake GraphQL server with GraphiQL, providing a full toolkit for schema management and testing, as listed in the features.
Can detect breaking changes and send notifications, often integrated into CI/CD pipelines to prevent issues before deployment, as emphasized in the README's use cases.
Limited to GraphQL APIs, making it unsuitable for projects using REST, gRPC, or other API types, which can be a drawback in diverse tech stacks.
Configuring notifications and CI/CD integration requires additional setup, such as linking to GitHub or other services, which may add overhead compared to simpler tools.
Relies on external schema sources or manual management, unlike some tools that offer integrated registries for better version control, as hinted by the promotion of GraphQL Hive.