javascript-dom-analysis

Detect frontend frameworks by analyzing JavaScript globals, DOM attributes, and bundle paths.

Updated May 27, 2026
One-click install
npx skills add https://github.com/hoanghn61/.agents --skill javascript-dom-analysis
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: javascript-dom-analysis
Source: https://github.com/hoanghn61/.agents/tree/main/skills/techstack-identification/javascript_dom_analysis
Command: npx skills add https://github.com/hoanghn61/.agents --skill javascript-dom-analysis

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you quickly determine which frontend frameworks and libraries power a website, reducing time spent on manual investigation and guesswork.

Core Features & Use Cases

  • Detects frameworks via runtime signals: Identifies likely technologies by matching JavaScript global variables and framework-specific hooks in the browser context.
  • Detects frameworks via DOM patterns: Finds framework-related DOM attributes and markers (including server-rendering and scoped-CSS conventions) to increase confidence.
  • Fingerprints builds and meta-frameworks: Infers bundlers and platforms from common asset paths and filenames (e.g., Next.js/_next, Nuxt/_nuxt), and checks for exposed source maps to assess implementation details and security exposure.
  • Use Case: You are auditing a competitor’s app and need to confirm whether it is using Next.js, Vue, or another stack, while also checking whether source maps are publicly accessible.

Quick Start

Use the javascript-dom-analysis skill to analyze a target website URL and return detected frameworks, bundle patterns, exposed source-map signals, and common analytics scripts.

Frequently Asked Questions about javascript-dom-analysis

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I detect which frontend framework a website is using?

Detect frontend frameworks by analyzing JavaScript globals, DOM attributes, and bundle path patterns across fetched web pages. This approach matches framework-specific variables and DOM markers to identify technologies like Next.js or Vue with higher confidence.

Can I check for exposed source maps when auditing a web application's frontend?

Yes, you can check for exposed source maps during frontend analysis. The process fingerprints builds and asset paths, then verifies whether source maps are publicly accessible to assess implementation details and security exposure.

What is bundle fingerprinting for technology reconnaissance?

Bundle fingerprinting is the process of inferring bundlers and meta-frameworks from common asset paths and filenames. It identifies platform signatures like Next.js/_next or Nuxt/_nuxt to build an accurate frontend inventory.

How do I perform a frontend inventory check for engineering or compliance workflows?

Perform a frontend inventory check by analyzing JavaScript globals and DOM attributes on target web pages. This evidence-based detection identifies active frameworks and exposed source maps, supporting engineering, marketing, and compliance audits.

Does DOM analysis require source map access to identify frameworks?

No, DOM analysis does not require source map access to identify frameworks. It detects technologies by matching JavaScript global variables and framework-specific DOM attributes, performing bundle checks separately to raise confidence.

Why does evidence-based framework detection require both global variables and DOM markers?

Evidence-based framework detection requires both global variables and DOM markers to prevent false positives. Requiring presence of framework-specific JavaScript globals alongside DOM attributes ensures accurate technology reconnaissance.