Every framework, platform and service we detect
81 curated technologies — web frameworks, CMSes, hosting, CDNs, analytics, payments, auth and the languages behind them — each with a page covering what it is, the detection signals, and how to confirm them yourself in DevTools.
What counts as a "technology" here
These are the framework- and platform-level fingerprints — the kind a tool like Wappalyzer catalogues — rather than individual npm packages (those live under /stack/npm) or WordPress plugins (under /stack/wordpress). Each page explains the concrete evidence Sourcemap Explorer reads: response headers, cookies, script-URL patterns, runtime globals, DOM markers, and — where the bundle ships sourcemaps — the original source paths that pin an exact version.
Frameworks & services (65)
Curated from the Wappalyzer catalogue. Each surfaces in the extension's Stack tab when its signals fire on a page.
Programming languages (16)
Inferred from headers, source extensions, sourcemap paths and runtime signals.
FAQ
How is a framework or platform detected on a site?
Sourcemap Explorer combines the vendored Wappalyzer fingerprint database (response headers, cookies, asset-URL prefixes, runtime globals and DOM markers) with sourcemap path matching against node_modules/<framework>/. When the framework maps to an npm package, the exact version comes from the embedded package.json — not a guess.
Why do some technologies redirect to an npm or WordPress page instead?
Several entries are the same real thing as a canonical npm package (react, next, vue, svelte) or a wp.org plugin (Yoast, WooCommerce, Elementor). To avoid duplicate content and consolidate ranking signals those /stack/tech/<name> URLs 301 to the canonical page, so they aren't listed twice here.
Can you detect a technology that isn't in this list?
Yes — anything in the Wappalyzer database resolves on demand at /stack/tech/<slug>, even when it isn't in the curated set below. The catalogue here is the subset that ships a hand-written editorial page.