panel tab · one of 9 10 sections free, no counter
Stack
What is this page built with, and has anything been published against those versions?
What the page is built with, what matched to prove it, and what has been published against those versions.
Reach it Press ⌘ + K on any tab and type stack. Ctrl + K on Windows and Linux
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.
in the panel · free, no counter
What the Stack tab is made of
10 sections, in the order the panel draws them- 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.
96 tools beside this tab · no host permissions · three free audits