openwebf-security-remote-content

Review security risks and mitigations for remote WebF content (untrusted bundles, URL allowlists, HTTPS, trust boundaries, clickjacking). Use when the user mentions untrusted remote bundles, bundle URL validation/allowlists, or remote updates risk.

⭐0stars🔀0forks📁View on GitHub🕐Updated Dec 20, 2025

When & Why to Use This Skill

This Claude skill provides a specialized security auditing framework for OpenWebF applications, focusing on the risks associated with remote content. It helps developers identify and mitigate vulnerabilities related to untrusted bundles, URL validation, and trust boundaries, ensuring that remote updates and web-based content remain secure and compliant with industry standards.

Use Cases

  • Scenario 1: Auditing remote bundle loading logic to ensure that only authorized, allowlisted URLs are accessed via HTTPS.
  • Scenario 2: Identifying and defining trust boundaries between native plugins and remote WebF content to prevent unauthorized access to device features.
  • Scenario 3: Reviewing application configurations to mitigate clickjacking and UI redressing risks in web-rendered interfaces.
  • Scenario 4: Validating remote update mechanisms against app store security guidelines to ensure compliance and prevent malicious code injection.
nameopenwebf-security-remote-content
descriptionReview security risks and mitigations for remote WebF content (untrusted bundles, URL allowlists, HTTPS, trust boundaries, clickjacking). Use when the user mentions untrusted remote bundles, bundle URL validation/allowlists, or remote updates risk.
allowed-toolsRead, Grep, Glob, mcp__openwebf__docs_search, mcp__openwebf__docs_get_section, mcp__openwebf__docs_related

OpenWebF Security: Remote Content & Trust Boundaries

Instructions

  1. Identify trust boundaries:
    • remote bundle URLs
    • user-generated content
    • bridge/native plugins
  2. Review how URLs are constructed and validated (allowlists, HTTPS, pinning/versioning).
  3. Use MCP docs (“Security”, “Store Guidelines”) as the baseline for recommendations.
  4. Provide remediation steps ordered by severity; do not modify files by default.

If the user is primarily asking about store policy/compliance for remote updates, prefer openwebf-security-store-guidelines.

More: