Jev credential shape review

Review a redacted code addition for credential handling

Describe the code addition with all secret values removed. Compare an embedded credential, environment lookup and nonfunctional placeholder before a local scanner handles the file.

Does the described addition contain a credential literal?Live API
Try an example

Only a redacted description is sent; the credential itself stays out of the input.

Source: Background discussion on X

Source and example scope

These six synthetic inputs and Choice rules are original demonstrations. The API-collected X post links to jev-commit, whose pinned README describes related checks using Noul questions. This page is not that hook, does not execute Git, and does not reproduce its measurements or credential-blocking policy.

Use the redacted description only; never infer a secret value.

Decision rules and labels
Credential literalEnvironment lookupPlaceholderNo credential cueNeed evidence
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

Review the context without uploading a secret.

The fixtures contain descriptions, variable names and explicit placeholders. The embedded-token case says that a value was written into code, but removes that value before the request. Do the same with your own input.

This page cannot establish whether a credential is real, active or exposed elsewhere. An environment lookup is only a statement about the supplied snippet; it does not prove that the application handles the resulting value safely.

Keep deterministic secret scanning close to the repository and let your own policy decide what blocks a commit. This original Choice demo provides a contextual review label and does not reproduce the source hook or its blocking behavior.

These six synthetic inputs and Choice rules are original demonstrations. The API-collected X post links to jev-commit, whose pinned README describes related checks using Noul questions. This page is not that hook, does not execute Git, and does not reproduce its measurements or credential-blocking policy.

Illustration of one spreadsheet row producing two separate classification results
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 redacted credential review.

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

    Add the information to check

    Describe the code addition with all secret values removed.

  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 Credential literal, Environment lookup, Placeholder, No credential cue, Need evidence. 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 Need evidence 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
Embedded token describedCredential literal99.0%
Environment variable readEnvironment lookup100%
Explicit examplePlaceholder100%
Ordinary constantNo credential cue99.0%
Unknown variable sourceNeed evidence98.0%
Private key describedCredential literal100%

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

Source and example scope

Replay the saved synthetic requests and compare each observed label with its authored expectation. Any disagreement stays visible; the model is not rerun to obtain a preferred answer.

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.

Runnable offline example

Run one sample, then inspect the local packet

View the code example
Single-request replay
npm install @typesafe-ai/sdk@0.6.0
# Set TYPESAFE_API_KEY privately in your shell.
node run-choice-sample.mjs samples.json case-1
python preview_choice_workflow.py samples.json saved-api-results.json
Scope of this demo

Where this decision fits

Useful scope

  • Distinguishing redacted literal descriptions from variable lookups
  • Explaining why a placeholder differs from an embedded credential
  • Adding contextual labels alongside a local scanner

Outside this demonstration

  • Submitting real API keys, passwords or private keys
  • Validating whether a credential is active or usable
  • Replacing deterministic scanning or guaranteeing leak prevention
Example FAQ

Questions about credential shape review.

Input scope and downstream handling determine what the label can tell you.

Should I paste a real credential to test this?

No. Remove the value locally and describe how it appears in the added code. The provided examples never need a real key.

Does Environment lookup mean the code is secure?

No. It describes the supplied line only. The application could still expose the value later, and that behavior is outside this input.

Is the leading probability an accuracy measurement?

No. It is the distribution for this request. Six synthetic fixtures check the workflow and preserve disagreements; they are not a production benchmark.

What happens if the API request fails?

The window shows an error and returns no fresh judgment. The replay runner makes one request without retries. A missing-evidence label is about the input, not a substitute for an API failure.

Try your own credential shape review input

Edit the supplied evidence above, or open the Playground for a different decision rule.