graphiql
An graphical interactive in-browser GraphQL IDE.
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:markdown-it | AI (dependencies): markdown-it is a well-known, widely-used Markdown parser with a long history and millions of weekly downloads. Its use in graphiql for rendering descriptions is legitimate and expected. | ai | |
| provenance | no-provenance | AI (provenance): graphiql is a long-established, high-trust package under the official graphql org; lack of Sigstore provenance is not a meaningful risk signal here. | ai | |
| phantom-deps | phantom-dep:markdown-it | AI (phantom-deps): markdown-it is a declared runtime dep used in the bundled output; phantom-dep flag reflects monorepo build structure, not a security issue. | ai | |
| phantom-deps | phantom-dep:graphql-language-service | AI (phantom-deps): graphql-language-service is a declared runtime dep in this monorepo package; phantom-dep flag is a build artifact, not a security concern. | ai |
Versions (showing 51 of 300)
| Version | Deps | Published |
|---|---|---|
| 5.2.3 | 4 / 18 | |
| 5.2.2 | 4 / 18 | |
| 5.2.1 | 4 / 18 | |
| 5.2.0 | 4 / 18 | |
| 5.1.1 | 4 / 18 | |
| 5.1.0 | 4 / 18 | |
| 5.0.6 | 4 / 18 | |
| 5.0.5 | 4 / 18 | |
| 5.0.4 | 4 / 18 | |
| 5.0.3 | 4 / 18 | |
| 5.0.2 | 4 / 18 | |
| 5.0.1 | 4 / 18 | |
| 5.0.0 | 4 / 18 | |
| 4.1.2 | 4 / 16 | |
| 4.1.1 | 4 / 21 | |
| 4.1.0 | 4 / 21 | |
| 4.0.5 | 4 / 21 | |
| 4.0.4 | 4 / 21 | |
| 4.0.3 | 4 / 21 | |
| 4.0.2 | 4 / 21 | |
| 4.0.1 | 3 / 20 | |
| 4.0.0 | 2 / 20 | |
| 3.9.0 | 2 / 22 | |
| 3.8.3 | 1 / 37 | |
| 3.8.2 | 1 / 37 | |
| 3.8.1 | 1 / 37 | |
| 3.8.0 | 1 / 37 | |
| 3.7.2 | 1 / 38 | |
| 3.7.1 | 1 / 38 | |
| 3.7.0 | 1 / 38 | |
| 3.6.0 | 1 / 38 | |
| 3.5.0 | 1 / 38 | |
| 3.4.1 | 1 / 38 | |
| 3.4.0 | 4 / 42 | |
| 3.3.2 | 4 / 42 | |
| 3.3.1 | 4 / 42 | |
| 3.3.0 | 4 / 42 | |
| 3.2.3 | 4 / 42 | |
| 3.2.2 | 4 / 42 | |
| 3.2.1 | 4 / 42 | |
| 3.2.0 | 4 / 42 | |
| 3.1.2 | 4 / 42 | |
| 3.1.1 | 4 / 42 | |
| 3.1.0 | 4 / 42 | |
| 3.0.10 | 4 / 42 | |
| 3.0.9 | 4 / 42 | |
| 3.0.8 | 4 / 42 | |
| 3.0.7 | 4 / 42 | |
| 3.0.6 | 4 / 42 | |
| 3.0.5 | 4 / 42 | |
| 3.0.4 | 4 / 42 |
v5.2.3
2 findingsThis version was published by a different npm account than previous versions on 2026-05-11. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.9.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.8.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.8.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.8.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.8.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.7.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.7.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.4.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.