How we detect every web technology — one per page
For each technology we can identify, here's the exact list of signals we look at, what they mean, how versioning works, and how to confirm the detection yourself in Chrome DevTools.
What "detection" means here
Detection on these pages is evidence, not a guess. Each guide lists the concrete signals that identify a technology — response headers, cookies, script-URL patterns, runtime globals, DOM markers and the original paths inside a JavaScript sourcemap — and spells out what each one actually proves about the page.
Where a site ships sourcemaps, detection gets sharper still: the bundled package.json gives the exact version, patch number included, instead of a best-guess range. And because every signal is something you can see in Chrome DevTools, each page doubles as a manual how-to — the extension just does it in one click.
Web framework
JavaScript framework
Detect React
The JavaScript library for building user interfaces — the base most meta-frameworks build on.
Detect Vue.js
Progressive JavaScript framework — the most popular alternative to React, especially in Asia and Europe.
Detect Svelte
Compile-time JavaScript framework — no runtime VDOM, components compile to direct DOM operations.
CMS
E-commerce
CSS framework
FAQ
Can Sourcemap Explorer detect any technology?
It detects anything with a recognisable signal. Around 7,500 frameworks, CMSes, hosts and services come from the vendored Wappalyzer fingerprint database, and any npm package or WordPress plugin resolves on demand from its sourcemap path or wp-content URL. A technology that ships no distinguishing header, cookie, asset path, global or source path can't be detected — by us or anyone else.
How accurate is the version it reports?
Exact, when the site ships a sourcemap that embeds the package's package.json — the version is read straight from the bundle. Without that, a version may be inferred from an asset URL (like a ?ver= query string) or omitted rather than guessed. Each detection page is explicit about which signal produced the number.
Do I need the extension, or can I detect this manually?
Every page documents the DevTools-only method first — the exact header, source path or global to look for — so you can confirm a detection by hand. The extension just automates that lookup across all signals at once and reads embedded versions for you.