HTML sanitization path: six recorded examples
The downloads contain six original inputs, their expected labels and one recorded API observation per input revision. Disagreements stay visible.
Show the content source, transformations and final DOM sink. Compare sanitized HTML with raw external markup, escaped text or an unresolved sanitizer contract.
The final sink determines whether content is interpreted as markup. A normal escaped text node differs from a raw HTML insertion API, even when both receive a string.
Follow transformations after sanitization too. Appending unsanitized content afterward can leave the final value outside the earlier sanitizer's contract.
The source linter checks unsanitized external HTML paths. These examples contain descriptions rather than executable attack strings. The result is a review cue, not a claim that a site passed an XSS assessment.
This is an independently authored text demonstration inspired by the linked X discussion. Its rules and synthetic inputs are ours. It does not reproduce the author’s application, verify reported outcomes, or perform an external action.

Use the sample to understand the rule, then test your own input for html sanitization path.

Show the content source, transformations and final DOM sink.

Open the decision rules and keep the intended distinction between Sanitized HTML, Raw external HTML, Text or constant, Review. Edit the choices only when testing your own rule.

Use a sample first, then try your own input. Compare the selected label with the other returned probabilities.

Review Review before using a result. The label is a decision about the supplied information, not an executed action.
| Original input | Observed label | Leading probability |
|---|---|---|
| CMS text in a raw sink | Raw external HTML | 99.0% |
| Explicit sanitizer path | Sanitized HTML | 97.0% |
| Framework text node | Text or constant | 98.0% |
| Trusted static markup | Text or constant | 69.0% |
| Unknown clean helper | Review | 86.0% |
| Raw content appended afterward | Raw external HTML | 91.0% |
These are six original synthetic inputs, tested once per request revision. The percentage is the leading option probability, not measured accuracy. Authored expectations and any disagreements remain in the downloadable evidence. 6 of 6 results matched the authored fixture expectations.Verified
The downloads contain six original inputs, their expected labels and one recorded API observation per input revision. Disagreements stay visible.
The single-request SDK runner uses your private TYPESAFE_API_KEY. The offline consumer reads saved observations, checks request hashes and prints a pending output. It does not call the model or change any external system.
# Offline: inspect the downloaded saved observations. No API key is needed.
python preview_choice_workflow.py samples.json saved-api-results.json
# Optional live request: install the SDK and set TYPESAFE_API_KEY privately.
npm install @typesafe-ai/sdk@0.6.0
node run-choice-sample.mjs samples.json case-1
# The live response prints to the terminal; it does not update saved-api-results.json.The input contract and these limits define what the result means.
No. Type validation says what kind of value it is, not which markup it contains or how the DOM will interpret it.
No. It describes the supplied path and sanitizer contract. Configuration, browser behavior and other sinks require separate verification.
It describes the distribution over the supplied choices for this request. These six synthetic examples are functional tests with authored expectations, not a production accuracy benchmark.
No. The demo displays a label and distribution. The downloadable consumer produces a pending preview packet. Application code and a separate authorization policy would control any real action.
Edit the example above to see how a changed fact affects the decision, or open the Playground for another task.