react-doctor/iframe-missing-sandbox

Add sandbox="" (or a curated, minimal set of allow- tokens) to your iframe to restrict embedded content.

Validation prompt

Confirm the detector match and collect the required evidence before deciding whether an edit is warranted.

Fires on a JSX <iframe> (or React.createElement("iframe", ...)) in three cases: no sandbox attribute at all; a sandbox string containing a token that isn't "" or a known allow-* value; or the allow-scripts + allow-same-origin pair, which together let the frame remove its own sandbox. A bare sandbox / sandbox={true} (present with no string value) passes, and document.createElement("iframe") is intentionally ignored.

Suppress when: a dynamic value the static check can't resolve to a string literal (sandbox={computedTokens} or sandbox={someVar}) is skipped, so a real misconfiguration assembled at runtime won't be caught: and conversely a present-but-empty literal is treated as safe.

Evidence boundary

The diagnostic proves only that the detector’s modeled source pattern matched. It does not prove runtime impact, product intent, rendered failure, or that one remediation is correct.

Establish the environment, repository policy, exceptions, and required rendered or runtime evidence before deciding the occurrence.

Record one outcome:

• Confirmed failure: The required evidence establishes the violation.
• Rejected: A documented exception or false-positive predicate applies.
• Needs evidence: Named evidence can still be collected.
• Unavailable: Required evidence cannot be collected in this run.
• Waived with evidence: An authorized, scoped exception applies to an established failure.
• Observation: The review records an optional tradeoff without claiming a defect.

A waiver records its scope, authority, evidence, and review condition. It is not a pass or false positive.

Default severity is registry metadata. Use the occurrence’s JSON severity after repository configuration when ordering real findings.

Fix prompt

Apply this candidate correction only after the required evidence confirms the risk.

Add a sandbox attribute and grant only the minimal capabilities the embed needs: start from sandbox="" (fully locked down) and add allow-* tokens one at a time, e.g. <iframe sandbox="allow-forms allow-popups" />. Never combine allow-scripts with allow-same-origin for untrusted content, since the frame can then reach into its parent origin and strip the sandbox. Use only valid tokens (allow-forms, allow-scripts, allow-popups, allow-same-origin, etc.) and drop anything misspelled. See https://oxc.rs/docs/guide/usage/linter/rules/react/iframe-missing-sandbox

Repository-wide copy prompt

Use this repository-wide prompt only after validating each occurrence. For one occurrence, use the guidance above.