Jev file path containment review

Review containment of an externally supplied file path

Show how the external name becomes the final opened path, including link and race controls. Compare enforced containment with a shown gap or unresolved path semantics.

file path containment reviewLive API
Try an example

The described path does not enforce its base directory.

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 file-operation boundary.

Decision rules and labels
ContainedGap shownNo external pathReview
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

Path containment is about the file ultimately opened, not simply the string that passed an earlier check. The input must explain normalization, links and the relationship between validation and the final operation.

A fixed mapping from safe identifiers to internal filenames can establish a different boundary from accepting arbitrary paths. The examples keep these contracts explicit rather than teaching an attack payload.

This exercise adapts a path-traversal review rule from the linked linter. It does not inspect a real filesystem, extract an archive or prove that production path handling is secure.

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 reviewing messages against supplied policy categories
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 file path containment.

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

    Add the information to check

    Show how the external name becomes the final opened path, including link and race controls.

  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 Contained, Gap shown, No external path, 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
Unbounded concatenationGap shown93.0%
Strict safe-name mappingContained62.0%
Final resolved containmentContained79.0%
Fixed internal fileNo external path89.0%
String-prefix checkReview86.0%
Unknown helperReview95.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

Example context 1

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 the contract of an upload or download path helper.
  • Separating external file content from an external file path.
  • Recording missing final-open assumptions before a security review.

Outside this demonstration

  • Using a semantic label instead of enforced filesystem containment.
  • Claiming link or race safety without an explicit implementation contract and tests.
Example FAQ

Using this example

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

Is a string-prefix check sufficient?

The string check alone does not describe the final filesystem operation. Normalization, directory separators, links and race behavior may matter.

Does this open or modify a file?

No. The demo classifies a supplied description. It performs no filesystem operation on the named path.

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.