Skip to content

panel tab · one of 10 10 sections 24-hour trial, then Pro

Stack

What is this page built with, and has anything been published against those versions?

What the page is built with, the marker that proves it, and what is published against those versions - read in your browser, no account.

Choosing between tools? LoupeKit vs Wappalyzer →

Reach it Press ⌘ + K on any tab and type stack. Ctrl + K on Windows and Linux

What each library is licensed under, what it trusts, what it duplicates, what it weighs
Stack What each library is licensed under, what it trusts, what it duplicates, what it weighs 10 sections

Every reading here is about trusting a detection. A framework named with nothing behind it is a guess printed confidently, so Technologies keeps what matched - the global, the attribute, the file name - beside the name it produced, and a version is only ever shown where something on the page actually carried one. Vulnerabilities takes those versions to published advisories, which is the only part of this tab that leaves the browser and the reason it runs on a press rather than on open. Headers and Pulse are already in hand: the response this page arrived under, and what it cost to draw.

section#sections

What the Stack tab is made of

Technologies
Everything detected on this page, grouped, with what matched.
Vulnerabilities
Dates the detected versions against published advisories. Runs on a press.
Lifecycle
Versions past end of life, and libraries nobody maintains any more. Offline.
Licences
What each detected technology is distributed under - copyleft, paid, or permissive.
Integrity
Cross-origin scripts and stylesheets, and whether the page asked for a hash to check them.
Bundle
Reads this page’s own scripts, from its own cache, and names what a bundler hid inside them.
Conflicts
Where two detected technologies are doing one job, and files loaded twice.
Weight
Which detected technology accounts for which part of the page’s download.
Headers
What this page’s own response headers permit. Already in hand - nothing extra is requested.
Pulse
Nodes, requests, bytes and paint timings for this load.
section#asked

Asked about this tab

Which technologies does it name, and how does it know?

Frameworks, libraries, tag managers, CMSs and hosts, each from the marker that matched - a global, an attribute, a file name, a header. The marker is kept beside the name, so a detection is something you can check rather than a label to trust.

Does it work on Firefox, and does it need access to every site?

It runs on Chromium browsers and on Firefox. It reads the tab you open it on, on your say-so, and asks for no website permission at install.

Does it need an account, and what leaves the browser?

No account. The detection runs in the browser. Only the advisory lookup in Vulnerabilities leaves it, and only when you press the button.

Is it a Wappalyzer alternative?

For naming one page's stack, yes: it shows the evidence for each detection and needs no sign-in. For prospect lists filtered by what sites run, no. The comparison page sets out where each is the better answer.

SAVE 33% €74.99 €49.99 Lifetime See the offer