Jev HTML sanitization path review

Trace external content through an HTML rendering path

Show the content source, transformations and final DOM sink. Compare sanitized HTML with raw external markup, escaped text or an unresolved sanitizer contract.

HTML sanitization path reviewLive API
Try an example

A string-type check does not sanitize markup.

Source: API-collected workflow inspiration; original demonstration below

Source and example scope

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.

Review the source-to-DOM path.

Decision rules and labels
Sanitized HTMLRaw external HTMLText or constantReview
A real response from the Jev API

Edit any input to explore a different decision. No request is sent until you run it.

Your next decision

Not run yet

Choose an example or write your own input, then run it to see the ranked choices.

Results are not stored by this site. Your submitted text is processed by the API provider.

The decision

What the decision checks

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.

Illustration of checking a code change and reviewing a flagged line
Illustration of the decision flow.
How it works

Try the example in four steps

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

  1. Illustration of adding the text or evidence for a decision

    Add the information to check

    Show the content source, transformations and final DOM sink.

  2. Illustration of defining a question and its allowed choices

    Confirm the question and labels

    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.

  3. Illustration of sending one input and comparing the returned choices

    Run the decision

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

  4. Illustration of reviewing a result and an uncertain item before using it

    Review the next step

    Review Review before using a result. The label is a decision about the supplied information, not an executed action.

Our API test

Recorded API observations

Recorded API observations
Original inputObserved labelLeading probability
CMS text in a raw sinkRaw external HTML99.0%
Explicit sanitizer pathSanitized HTML97.0%
Framework text nodeText or constant98.0%
Trusted static markupText or constant69.0%
Unknown clean helperReview86.0%
Raw content appended afterwardRaw external HTML91.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

Understand the results

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.

Using the result in your application

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.

Replay options

Inspect saved outputs or request a new decision

View the code example
Two independent commands
# 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.
Scope of this demo

Where this decision fits

Useful scope

  • Reviewing CMS content before raw HTML rendering.
  • Checking whether a later transformation bypasses an earlier sanitizer.
  • Distinguishing escaped text from interpreted HTML.

Outside this demonstration

  • Executing markup or testing a live site with a payload.
  • Treating a helper name or string schema as proof of complete XSS protection.
Example FAQ

Using this example

The input contract and these limits define what the result means.

Is checking that content is a string enough?

No. Type validation says what kind of value it is, not which markup it contains or how the DOM will interpret it.

Does Sanitized HTML certify the site?

No. It describes the supplied path and sanitizer contract. Configuration, browser behavior and other sinks require separate verification.

Does the leading probability measure accuracy?

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.

Will a result change an external system?

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.

Test a different input

Edit the example above to see how a changed fact affects the decision, or open the Playground for another task.