security.output-encoding

Avoid unsafe raw HTTP response output

Raw response writers should not echo request data into HTML-capable responses without trusted escaping or sanitization.

#Metadata

#Why it matters

Directly reflecting request data into HTML-capable response sinks creates reflected XSS and content injection risk.

#Remediation

Escape or sanitize the data with a trusted helper, or switch to a response format that does not treat it as executable markup.

#Repository path

The generated metadata points to critiq-rules/libs/rules/catalog/rules/typescript/ts.security.unsanitized-http-response.rule.yaml.