Code RadarLOCAL SAST GATE
AccountGitHubInstall Radar

Detect path traversal before merge.

See how path traversal fits local review, which evidence Code Radar produces, where coverage ends, and how trusted findings move into CI.

Check this risk locallyReview detection evidence
radar scan . --quick

What path traversal means here.

The path traversal rule identifies review patterns that can create exploitable behavior or hide material maintenance risk, then returns the affected location, severity, confidence, and remediation context.

Rule reference

Evidence to inspect

Use “Detect path traversal before merge.” as the scope for this decision: verify the input, finding detail, workflow handoff, and product boundary before you install or buy.

CriterionEvidence to inspectBoundary
Input scopeSelected files, configuration, scan mode, and enabled rules.Only included paths and configured checks are evaluated.
Finding detailFile, line, rule ID, severity, explanation, and repair direction.Illustrative output is not a result from your repository.
Workflow handoffLocal result, report format, agent context, and optional CI signal.Enable exports or CI only when the workflow needs them.
Decision fitUse the same criteria on a real repository before choosing a plan or tool.No universal winner or guaranteed outcome is claimed.
Rule reference

Check this risk locally

Check this risk locally

Coverage and concrete signals

Detect request paths escaping an intended directory boundary.

  • Audience: Developers and reviewers deciding how to handle path traversal findings before merge.
  • Evidence to inspect before you trust the result.: Check how request paths are resolved against the base directory and verify that the safer example rejects paths outside that boundary.
  • Boundary: A trusted identifier or a resolver that canonicalizes and enforces containment can avoid a finding; verify symlink and encoded-path cases before suppressing.
  • Rule ID: RADAR-SEC-PATH
Feature: security scannerChoose the next page that matches the remaining implementation or evaluation step.Feature: sastChoose the next page that matches the remaining implementation or evaluation step.Docs: rulesChoose the next page that matches the remaining implementation or evaluation step.

Risky pattern / Safer pattern

path traversal: A useful result must be explainable to a developer and portable to the next review surface. Inspect the concrete evidence below before changing team policy.

Risky patternSafer pattern
readFile(baseDir + request.path);readFile(resolveInside(baseDir, request.path));

From local signal to shared gate.

path traversal: Use the smallest workflow that proves value. Each later step should reuse evidence the team already understands. Check how request paths are resolved against the base directory and verify that the safer example rejects paths outside that boundary.

StepCommand or actionDecision
1Run a quick local scanIs the signal useful?
2Inspect and repair findingsIs the fix specific and reproducible?
3Export portable evidenceDoes the reviewer need SARIF, JSON, or HTML?
4Promote the trusted threshold to CIWhich severity should block a pull request?
radar scan . --quick
radar scan . --format sarif --fail-on high
Official source

Primary sources

Rule reference

Start with the problem you need to solve.

Open page →
Local SASTLocal SAST for Developers and CIProofSee sample reportInstallInstall Radar

Validate the workflow on your own code.

Apply this page’s evidence to one real repository. For “Detect path traversal before merge.”, confirm which finding is produced, whether the proposed next step is reproducible, and where local scanning, reports, agents, or CI should stop or expand.

Check this risk locallyReview detection evidence