jxscout-static-analysis

Queries and tracks jxscout static analysis matches for JavaScript and HTML.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Security teams and engineers waste significant time manually sifting through unstructured static analysis matches from jxscout when triaging code vulnerabilities and exploring application attack surfaces, leading to delayed response to high-risk findings.

Core Features & Use Cases

  • Match Discovery & Filtering: List all available match kinds and query matches with granular filters (file path, value substring, seen status, file type) to focus on high-priority security findings like exposed secrets or dangerous HTML manipulation patterns.
  • Triage Progress Tracking: Mark individual or bulk matches as seen or unseen to track review progress across vulnerability triage sessions, ensuring no unreviewed high-risk findings are missed.
  • Use Case: A security engineer can use this skill to quickly pull all unseen secret matches from authentication-related JS files to prioritize credential exposure risks, then mark them as seen after review.

Quick Start

Use the jxscout-static-analysis skill to pull all unseen secret matches from files in the auth directory and mark them as seen after you finish reviewing each finding.

Frequently Asked Questions about jxscout-static-analysis

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

FAQPage Schema
What is the best way to track vulnerability review progress across static analysis scans?

Filter static analysis matches by file path, value substring, seen status, and file type to isolate high-priority security findings in JavaScript and HTML codebases. You can then track review progress by marking individual or bulk matches as seen after investigating each vulnerability.

Does this triage process support cross-referencing matches with HTTP request context?

Filter static analysis matches to show unseen secrets in specific directories by applying file path and seen status filters. This allows you to prioritize credential exposure risks in targeted areas like authentication folders before marking them as seen after review.

How do I manage attack surface exploration for web applications using static analysis results?

Manage attack surface exploration by listing available match kinds and querying static analysis results with granular filters. This process exposes dangerous HTML manipulation patterns and security findings, helping you systematically review web application vulnerabilities.

What are the limitations of manually triaging unstructured static analysis matches?

Manually triaging unstructured static analysis matches wastes significant time and delays response to high-risk findings. Without granular filtering and progress tracking, security teams struggle to ensure no unreviewed vulnerabilities are missed during attack surface exploration.