@graphql-inspector/core

v6.2.0

Tooling for GraphQL. Compare GraphQL Schemas, check documents, find breaking changes, find similar types. For more information about how to use this package see README

Latest version published 9 days ago

License: MIT

NPM

GitHub

Package Health Score

86 / 100

security
No known security issues
popularity
Popular
maintenance
Healthy
community
Sustainable

Explore Similar Packages

Security

No known security issues

All security vulnerabilities belong to production dependencies of direct and indirect packages.

Security and license risk for significant versions

All Versions

Version				Vulnerabilities	License Risk
6.2.0	\|	11/2024		0 C 0 H 0 M 0 L	0 H 0 M 0 L
6.1.0	\|	06/2024	Popular	0 C 0 H 0 M 0 L	0 H 0 M 0 L
5.0.2	\|	11/2023		0 C 0 H 0 M 0 L	0 H 0 M 0 L
4.2.2	\|	04/2023		0 C 0 H 0 M 0 L	0 H 0 M 0 L
4.1.1	\|	04/2023		0 C 0 H 0 M 0 L	0 H 0 M 0 L

License

MIT

Security Policy

Is your project affected by vulnerabilities?

Scan your projects for vulnerabilities. Fix quickly with automated fixes. Get started with Snyk for free.

Get started free

Popularity

Popular

Weekly Downloads (230,251)

GitHub Stars: 1.65K
Forks: 185
Contributors: 80

Direct Usage Popularity

The npm package @graphql-inspector/core receives a total of 230,251 downloads a week. As such, we scored @graphql-inspector/core popularity level to be Popular.

Based on project statistics from the GitHub repository for the npm package @graphql-inspector/core, we found that it has been starred 1,652 times.

Downloads are calculated as moving averages for a period of the last 12 months, excluding weekends and known missing data points.

Community

Sustainable

Readme.md: Yes
Contributing.md: No
Code of Conduct: No
Contributors: 80
Funding: Yes

With more than 10 contributors for the @graphql-inspector/core repository, this is possibly a sign for a growing and inviting community.

We found a way for you to contribute to the project! Looks like @graphql-inspector/core is missing a Code of Conduct.

Embed Package Health Score Badge

Maintenance

Healthy

Commit Frequency

Open Issues: 81
Open PR: 35
Last Release: 9 days ago
Last Commit: 9 days ago

Further analysis of the maintenance status of @graphql-inspector/core based on released npm versions cadence, the repository activity, and other data points determined that its maintenance is Healthy.

We found that @graphql-inspector/core demonstrates a positive version release cadence with at least one new version released in the past 3 months.

As a healthy sign for on-going project maintenance, we found that the GitHub repository had at least 1 pull request or issue interacted with by the community.

Keep your project healthy

Check your package.json

Ensure all the packages you're using are healthy and well-maintained

Snyk Vulnerability Scanner

Get health score & security insights directly in your IDE

Package

Node.js Compatibility: >=18.0.0

Age: 6 years
Dependencies: 3 Direct
Versions: 429
Install Size: 564 kB
Dist-tags: 5
# of Files: 200
Maintainers: 3
TS Typings: Yes

@graphql-inspector/core has more than a single and default latest tag published for the npm package. This means, there may be other tags available for this package, such as next to indicate future releases, or stable to indicate stable releases.

Not sure how to use @graphql-inspector/core?

To help you get started, we've collected the most common ways that @graphql-inspector/core is being used within popular public projects.

kamilkisiela / graphql-inspector / packages / cli / __tests__ / render.ts View on Github

test('render breaking', () => {
  const change: Change = {
    criticality: {
      level: CriticalityLevel.Breaking,
    },
    type: ChangeType.TypeRemoved,
    message: 'Boom, breaking',
    path: 'Type.field',
  };

  const [symbol, msg] = renderChange(change);

  expect(symbol).toBeDefined();
  expect(symbol).toEqual(getSymbol(CriticalityLevel.Breaking));

  expect(msg).toBeDefined();
  expect(msg).toEqual(change.message);
});

View more ways to use @graphql-inspector/core

GraphQL Inspector

GraphQL Inspector outputs a list of changes between two GraphQL schemas. Every change is precisely explained and marked as breaking, non-breaking or dangerous. It helps you validate documents and fragments against a schema and even find similar or duplicated types.

Features

Major features:

Compares schemas
Finds breaking or dangerous changes
Validates documents against a schema
Finds similar / duplicated types
Schema coverage based on documents
Serves a GraphQL server with faked data and GraphQL Playground

GraphQL Inspector has a CLI and also a programmatic API, so you can use it however you want to and even build tools on top of it.

Installation

pnpm add @graphql-inspector/core

Examples

import {
  diff,
  validate,
  similar,
  coverage,
  Change,
  InvalidDocument,
  SimilarMap,
  SchemaCoverage
} from '@graphql-inspector/core'

// diff
const changes: Change[] = diff(schemaA, schemaB)
// validate
const invalid: InvalidDocument[] = validate(documentsGlob, schema)
// similar
const similar: SimilarMap = similar(schema, typename, threshold)
// coverage
const schemaCoverage: SchemaCoverage = coverage(schema, documents)
// ...

License

@graphql-inspector/core dependencies

dependency-graph object-inspect tslib

FAQs

What is @graphql-inspector/core?

Tooling for GraphQL. Compare GraphQL Schemas, check documents, find breaking changes, find similar types. Visit Snyk Advisor to see a full health score report for @graphql-inspector/core, including popularity, security, maintenance & community analysis.

Is @graphql-inspector/core popular?

The npm package @graphql-inspector/core receives a total of 230,251 weekly downloads. As such, @graphql-inspector/core popularity was classified as a popular. Visit the popularity section on Snyk Advisor to see the full health analysis.

Is @graphql-inspector/core well maintained?

We found that @graphql-inspector/core demonstrated a healthy version release cadence and project activity. It has a community of 80 open source contributors collaborating on the project. See the full package health analysis to learn more about the package maintenance status.

Is @graphql-inspector/core safe to use?

The npm package @graphql-inspector/core was scanned for known vulnerabilities and missing license, and no issues were found. Thus the package was deemed as safe to use. See the full health analysis review.

Last updated on 21 November-2024, at 05:24 (UTC).

Build a secure application checklist

Select a recommended open source package

Minimize your risk by selecting secure & well maintained open source packages

DONE

Scan your app for vulnerabilities

Scan your application to find vulnerabilities in your: source code, open source dependencies, containers and configuration files

SCAN NOW

Fix identified vulnerabilities

Easily fix your code by leveraging automatically generated PRs

AUTO FIX

Monitor for new issues

New vulnerabilities are discovered every day. Get notified if your application is affected

MONITOR APP

Package Health Score

Explore Similar Packages

Security and license risk for significant versions

Is your project affected by vulnerabilities?

Weekly Downloads (230,251)

Direct Usage Popularity

Embed Package Health Score Badge

Commit Frequency

Keep your project healthy

Check your package.json

Snyk Vulnerability Scanner

Not sure how to use @graphql-inspector/core?

GraphQL Inspector

Features

Installation

Examples

License

@graphql-inspector/core dependencies

FAQs

What is @graphql-inspector/core?

Is @graphql-inspector/core popular?

Is @graphql-inspector/core well maintained?

Is @graphql-inspector/core safe to use?

Build a secure application checklist

Select a recommended open source package

Scan your app for vulnerabilities

Source Code

Open Source

Container

Config

Fix identified vulnerabilities

Monitor for new issues