jxscout-relationships

Map JavaScript files, iframes, and source map connections for web assets.

11|1|Updated May 4, 2026
One-click install
npx skills add https://github.com/dreadnode/capabilities --skill jxscout-relationships
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: jxscout-relationships
Source: https://github.com/dreadnode/capabilities/tree/main/capabilities/web-security/skills/jxscout-relationships
Command: npx skills add https://github.com/dreadnode/capabilities --skill jxscout-relationships

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manually tracing how web assets like JavaScript files, iframes, and source maps connect across a page is time-consuming and error-prone, especially when scoping an attack surface for web security testing.

Core Features & Use Cases

  • Loaded JS File Mapping: Retrieve all JavaScript files loaded by a target HTML page, including reversed source map files, to focus analysis on relevant runtime code.
  • Impact Assessment: Identify which HTML pages load a specific JavaScript file to understand the blast radius of a potential vulnerability.
  • Iframe Analysis: List all iframes embedded by a page to assess postMessage risks, cross-origin interactions, and clickjacking vulnerabilities.
  • Use Case: When testing a customer-facing web application, use this skill to map all assets on the login page to identify exposed debug endpoints in lazy-loaded chunks and cross-origin iframes that could be leveraged for attacks.

Quick Start

Use the jxscout-relationships skill to map all JavaScript files and embedded iframes loaded by your target web application's homepage to scope your attack surface.

Frequently Asked Questions about jxscout-relationships

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

FAQPage Schema
How do I map web asset relationships for attack surface analysis?

Attack surface scoping identifies all JavaScript files, embedded iframes, and reversed source maps loaded by a target HTML page to expose interconnected frontend assets. This reveals runtime code connections and cross-origin interactions for security testing without manual browser inspection.

How can I find which HTML pages load a specific JavaScript file?

To find which HTML pages load a specific JavaScript file, query asset relationship data to identify every page executing that script. This impact assessment reveals the blast radius of potential vulnerabilities and exposed debug endpoints across the application.

Why do I need to analyze embedded iframes for web security testing?

Analyzing embedded iframes is necessary to assess postMessage risks, cross-origin interactions, and clickjacking vulnerabilities. Mapping embedded frames reveals how untrusted origins interact with the parent application, exposing potential cross-origin attack vectors.

What is reversed source map analysis in JavaScript security testing?

Reversed source map analysis retrieves original source code from compiled bundles to focus analysis on relevant runtime code. Mapping these connections helps identify exposed debug endpoints hidden within lazy-loaded chunks on customer-facing web applications.

Do I need a specific environment setup to map JavaScript asset relationships?

Mapping JavaScript asset relationships requires the JXSCOUT_PROJECT_NAME environment variable and jxscout-pro-v2 client mode. This setup enables direct querying of asset relationship data, eliminating manual browser inspection during penetration testing.

What is the best way to identify exposed debug endpoints in lazy-loaded JavaScript chunks?

The best way to identify exposed debug endpoints in lazy-loaded chunks is mapping all JavaScript files and reversed source maps loaded by a target page. This reveals hidden runtime code connections and scopes the attack surface of customer-facing web applications.