graphql
A Query Language and Runtime which can target any service.
About
A Query Language and Runtime which can target any service.
What detecting graphql tells you about a site
graphql is the reference JavaScript implementation of the GraphQL spec: the parser, type system, validation and execution engine. Finding it tells you the app speaks GraphQL, and how it appears matters: bundled into the client it usually backs a query client building and parsing operations, while on the server it indicates a schema-first or code-first GraphQL API. Either way it signals a team that chose GraphQL's typed, query-shaped data model over plain REST, which often correlates with complex, relational data needs and a deliberate API-design culture.
Why the exact graphql version matters
The graphql package is a peer dependency for almost every client and server tool in the ecosystem, and major versions (notably the v15-to-v16 line and beyond) tightened the API and removed deprecated exports, so the version is load-bearing: mismatches cause the classic duplicate-graphql and peer-dependency failures. Reading it tells you which spec generation and which surrounding tooling era the project sits in.
graphql in a real-world stack
When you find graphql in a bundle, it rarely travels alone. @apollo/client, urql, graphql-request or a server like Apollo Server or graphql-yoga.
Quick facts
npm install graphqlThis package powers GraphQL
The graphql package is the canonical implementation of GraphQL. Sourcemap Explorer uses this exact npm package as the framework-level fingerprint when it flags GraphQL on a page — both via the bundled node_modules/graphql/ source paths and via the embedded package.json inside the JavaScript sourcemap.
How Sourcemap Explorer detects graphql
graphql ships as v17.0.2, published 2026-07-03 and carries 0 direct dependencies, 299 versions on the registry. Those exact numbers are the footprint Sourcemap Explorer matches when graphql rides inside a deployed bundle — here is how the detection works.
We catch graphql from two complementary signals: bundled source paths and the embedded package.json. Modern bundlers (webpack, Vite, esbuild, Rollup, Turbopack) preserve the original node_modules/graphql/ paths inside the JavaScript sourcemap's sources[] array — that's the canonical signal. When the matching package.json is also captured in sourcesContent[], we read the exact version field — patch number included. No regex guessing, no version inference.
- 1
Confirm the site exposes sourcemaps
In DevTools Network, check the response headers of any application script for `SourceMap` or `X-SourceMap`. Failing that, fetch the script's last 4 KB and look for a `//# sourceMappingURL=` comment — that map is where the `graphql` paths live.
- 2
Find the package in the bundle
Open DevTools → Network → reload. Click any application script and look at its sourcemap. Inside, search `sources[]` for entries matching `node_modules/graphql/` — every match confirms the package is bundled. The matching `sourcesContent[i]` for `node_modules/graphql/package.json` gives you the exact installed version.
- 3
Read the version directly from package.json
Run `jq -r '. as $m | $m.sources | to_entries[] | select(.value | endswith("node_modules/graphql/package.json")) | $m.sourcesContent[.key] | fromjson | .version' bundle.js.map`. Sourcemap Explorer automates the same query in the popup.
Major releases of graphql
When each major version first landed. Major bumps are where breaking changes live, so this timeline is the fastest way to date the graphql version a site actually ships against the ecosystem.
Recent security advisories for graphql
The 1 most recent advisories affecting some versions of graphql, aggregated from OSV.dev (GitHub Advisory + CVE data). A listing here doesn't mean the version a given site ships is affected — each advisory applies to a specific version range. Sourcemap Explorer reads the exact bundled version so you can check it against these ranges.
graphql Uncontrolled Resource Consumption vulnerability
Recent versions
FAQ
What is graphql used for?
A Query Language and Runtime which can target any service.
How can I tell if a website is using graphql?
Open the page in Chrome with the Sourcemap Explorer extension installed and read the Stack tab. We catch `graphql` from two complementary signals: `node_modules/graphql/` paths inside the JavaScript sourcemap, and the embedded `package.json` we read for exact-version detection. Without the extension you can do the same lookup manually in DevTools — the steps are listed in the "How Sourcemap Explorer detects" section above.
How do I find out which version of graphql a website is running?
Read it straight from the site's JavaScript sourcemap. When a build ships source maps, the bundled `graphql/package.json` carries the exact `version` string — Sourcemap Explorer extracts it in one click on the Stack tab, and you can do it by hand in DevTools by opening the `.map` file and searching for `node_modules/graphql/package.json`. That is far more reliable than inferring the version from an asset-hash or a `?ver=` query string, which is all surface-level detectors have to go on. The current npm release is 17.0.2, but real deployments frequently run an older pinned version — which is exactly why reading the bundled number matters.
What is the latest version of graphql?
17.0.2, as published on the npm registry. The "Recent versions" table on this page lists the most recent 8 releases with their release dates. Sourcemap Explorer reports the version actually bundled into a site, which can lag the latest release by months on real-world deployments.
Is graphql actively maintained?
Very actively maintained — the last release shipped within the past three months. The last published release was 2026-07-03. Source code: https://github.com/graphql/graphql-js.
What is the relationship between graphql and GraphQL?
graphql is the canonical npm package for GraphQL. Sourcemap Explorer treats finding `graphql` in a bundle as the framework-level signal that GraphQL is on the page, and the page you're reading is the canonical Sourcemap Explorer entry for the package itself.
Does graphql have known security vulnerabilities?
1 recent advisory affecting some versions of graphql is listed in the "Recent security advisories" section above, aggregated from OSV.dev (GitHub Advisory + CVE data). Whether a particular site is exposed depends entirely on the exact version it ships — each advisory applies to a specific version range, not to the package as a whole. That is why the precise bundled version matters: Sourcemap Explorer reads the version a site actually runs, so you can check it against the affected ranges instead of assuming the latest release is what's deployed.
Where can I read more?
Project homepage: https://github.com/graphql/graphql-js. Source code: https://github.com/graphql/graphql-js. Published on npm: https://www.npmjs.com/package/graphql. Licensed as MIT.
Keep reading on Sourcemap Explorer
Practical guides
Detection deep dives
Alternative tools
Detected by Sourcemap Explorer
When a bundle ships sourcemaps, we read the embedded package.json for graphql and report the precise version (the registry's latest is v17.0.2, published 2026-07-03; the bundled copy is often older). Without sourcemaps, an import / require in the page's scripts is enough to flag it.