security-review-owasp-third-party-javascript-management

Review third-party JavaScript management risks in web applications.

Updated Mar 26, 2026
One-click install
npx skills add https://github.com/sjinks/ai-owasp-skillset --skill security-review-owasp-third-party-javascript-management
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: security-review-owasp-third-party-javascript-management
Source: https://github.com/sjinks/ai-owasp-skillset/tree/main/.github/skills/security-review-owasp-third-party-javascript-management
Command: npx skills add https://github.com/sjinks/ai-owasp-skillset --skill security-review-owasp-third-party-javascript-management

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps reviewers find security weaknesses in web applications that rely on third-party JavaScript, browser policies, and client-side trust boundaries.

Core Features & Use Cases

  • Script Trust Review: Inspect third-party scripts, widgets, and browser integrations for unsafe loading, excessive privilege, and supply-chain exposure.
  • Browser Boundary Analysis: Evaluate DOM sinks, storage, messaging, framing, and cross-origin behavior for injection or data leakage risks.
  • Security Review Output: Produce evidence-based findings, review gaps, and passed checks tailored to OWASP Third-Party JavaScript Management guidance.

Quick Start

Ask this skill to review the attached web app or page flow for third-party JavaScript management issues and return confirmed findings, gaps, passed checks, and a concise overall assessment.

Frequently Asked Questions about security-review-owasp-third-party-javascript-management

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

FAQPage Schema
How do I review third-party JavaScript security risks in my web application?

Reviewing third-party JavaScript security risks involves evaluating script loading, DOM sinks, browser policies, and cross-origin behavior to identify injection or data leakage paths. This Skill inspects widgets and dependencies for unsafe loading, excessive privilege, and supply-chain exposure.

What does a browser boundary analysis cover for client-side trust validation?

Browser boundary analysis covers DOM sinks, storage, messaging, framing, and cross-origin behavior. It evaluates client-side state and trust boundaries to detect injection risks and data leakage paths during security reviews of browser-rendered pages and response policies.

How do I check Content Security Policy and cross-origin framing for script injection vulnerabilities?

Checking CSP and cross-origin framing requires evidence-based assessment of browser policies, DOM sinks, and third-party dependencies. This Skill separates confirmed findings from review gaps, evaluating script loading and messaging behavior against OWASP Third-Party JavaScript Management guidance.

Can I assess supply-chain exposure from external scripts and widgets during a security audit?

Yes, assessing supply-chain exposure from external scripts is a core function. The Skill inspects third-party scripts and browser integrations for unsafe loading and excessive privilege, producing passed checks and an overall assessment tailored to OWASP guidelines.

What is the best way to document DOM injection and data leakage findings in a security review?

Documenting DOM injection and data leakage findings requires separating confirmed evidence from review gaps. This Skill outputs structured findings, passed checks, and a concise overall assessment based on evaluated trust boundaries and leakage paths.

Why does my third-party JavaScript management review need to separate confirmed findings from gaps?

Separating confirmed findings from gaps ensures an evidence-based assessment of DOM sinks, browser policies, and trust boundaries. This distinction prevents false positives in script trust reviews and clarifies which third-party dependency risks still require further evaluation.