Frontend Tech-Stack Identification
Scope
Identify client-side technologies: JavaScript frameworks (React, Vue, Angular, Svelte), meta-frameworks (Next.js, Nuxt, Gatsby, Remix), CSS frameworks (Tailwind, Bootstrap, Material UI), state management, build tools, CMS generators, and analytics SDKs from rendered HTML/JS.
Signals (input)
- HTTP response bodies (HTML)
- JavaScript global variables (
window.*)
- DOM attributes (
data-*, ng-*, _ngcontent-*)
- Script src URL patterns (
/_next/, /wp-content/, etc.)
<meta name="generator"> tags- HTML comments
- CSS class patterns
- JSON-LD / structured data
- Source map exposure
Inferences (output)
- JS framework + version (e.g. React 18.2)
- Meta-framework (implies host framework — Next.js → React)
- CMS / static site generator (WordPress, Drupal, Hugo, Ghost)
- CSS framework + UI library
- Build tool (Webpack, Vite, Parcel)
- Analytics / tracking SDKs (GA, Mixpanel, Hotjar, FullStory)
- Source map exposure (security finding)
Techniques
See reference/patterns.md.
When to use
- Phase 2/3 of a tech-stack OSINT engagement
- Mapping client-side attack surface for XSS / DOM-based testing
- Validating CMS/version for CVE matching
- Identifying SaaS dependencies via third-party scripts
1---2name: techstack-frontend3description: Frontend tech-stack identification — JavaScript frameworks, meta-frameworks, CSS frameworks, UI libraries, build tools, and CMS via DOM, JS globals, HTML, and bundle patterns.4---5
6# Frontend Tech-Stack Identification
7
8## Scope
9
10Identify client-side technologies: JavaScript frameworks (React, Vue, Angular, Svelte), meta-frameworks (Next.js, Nuxt, Gatsby, Remix), CSS frameworks (Tailwind, Bootstrap, Material UI), state management, build tools, CMS generators, and analytics SDKs from rendered HTML/JS.
11
12## Signals (input)
13
14- HTTP response bodies (HTML)
15- JavaScript global variables (`window.*`)
16- DOM attributes (`data-*`, `ng-*`, `_ngcontent-*`)
17- Script src URL patterns (`/_next/`, `/wp-content/`, etc.)
18- `<meta name="generator">` tags
19- HTML comments
20- CSS class patterns
21- JSON-LD / structured data
22- Source map exposure
23
24## Inferences (output)
25
26- JS framework + version (e.g. React 18.2)
27- Meta-framework (implies host framework — Next.js → React)
28- CMS / static site generator (WordPress, Drupal, Hugo, Ghost)
29- CSS framework + UI library
30- Build tool (Webpack, Vite, Parcel)
31- Analytics / tracking SDKs (GA, Mixpanel, Hotjar, FullStory)
32- Source map exposure (security finding)
33
34## Techniques
35
36See [reference/patterns.md](reference/patterns.md).
37
38## When to use
39
40- Phase 2/3 of a tech-stack OSINT engagement
41- Mapping client-side attack surface for XSS / DOM-based testing
42- Validating CMS/version for CVE matching
43- Identifying SaaS dependencies via third-party scripts
transilienceai