Skip to main content
Use SAST to find vulnerabilities in source code and application logic before release. Scan a full branch for a baseline, use PR scanning to review changes, and check each finding’s evidence before deciding how to fix it.

Run your first scan

1

Connect a repository

Follow Quick Start to connect your repository to ZeroPath.
2

Check the scan settings

Open the repository’s Settings. Under Full scans, open Full Scan Issue Types and check that SAST is selected. SAST is on by default. Repository settings can inherit organization or tag settings. For a broader review, set Analysis → Full scan mode to Standard. See scanner settings.
3

Scan a branch

Select Scan repository, choose the branch you want to review, and select Start Scan. In Scans, select the completed run and choose Open in Issues to see its findings.

Choose when to scan

Standard runs broader discovery, including configured custom rules. Lightweight looks for known patterns and validates its matches with AI. Eligible follow-up scans can verify fixes in changed files. See full scan modes for the differences.

Review and fix findings

  1. In Issues, choose SAST for technical vulnerabilities or Logic for application logic. Use the repository, branch, or scan source filters to narrow your review. Start with the Fix now lane for high- or critical-severity findings with exploit evidence.
  2. Open a finding. Read Overview and Evidence to understand what was found and how it was assessed. Check History for earlier detections or triage decisions.
  3. Open Fix to review remediation guidance or a patch. Generate and review a patch where offered, or make the change yourself. To check a fix for an existing finding, reference it in your PR and follow Fix Verification. The pre-merge result is informational. Verification on the target branch can resolve the finding after merge.
For triage actions, evidence labels, and exports, see the Issues guide. For the patch workflow, see Auto-Fix & Patches.

If a result is missing or incomplete

How SAST works

ZeroPath uses static rules and AI-assisted analysis to find candidates and evaluate the affected code in context. The scan uses a specific commit. The scan type, selected modules, scope, and effective settings determine which analysis runs.

End-to-end scan flow

ZeroPath checks out the scan commit and applies the scan scope. Application discovery uses the repository structure to identify services and entry points. Use repository context to describe your architecture. Review the application threat model to correct how ZeroPath understands it. If an application directory disappears, ZeroPath skips it during scans and saves your edits to its overview and threat model for use if the directory returns.
Pattern analysis looks for known classes of vulnerability. Standard full scans can also investigate data flows and application logic, including checks that depend on how the application handles authorization or enforces business rules. A PR review starts from the changed files and checks relevant context. Custom rules and custom sources and sinks let you tune analysis to your code.
ZeroPath reviews candidates in context, combines overlapping detections, and records the evidence available for each reported finding. Later scans can link new detections to existing findings. Eligible rescans can reuse prior results on the same branch and focus on changed code. An incomplete or reduced-coverage scan can preserve earlier findings.A full scan can resolve an open SAST finding if Git history confirms that its primary file was removed from the branch. Deleting a file can leave a credential in Git history. Follow the secrets guidance for leaked credentials.

Understanding a finding

Severity and confidence

Severity is the CVSS base score, on a scale from 0 to 10. ZP Score combines severity and confidence on a scale from 0 to 100. Review the evidence as well as the scores when prioritizing findings. In Evidence → Severity / CVSS, you can review the CVSS 4.0 assessment and the CVSS 3.1 vector when available. Unassessed means a severity score is unavailable. See the ZeroPath score guide for how missing confidence affects the composite score.

Reinvestigate a finding

Choose Reinvestigate from the finding’s More actions menu if you have the Close Issues permission. When the review finishes, check Evidence → Investigation for the verdict and reasoning. An inconclusive review leaves the finding for your team to evaluate. If the source branch has been removed, check whether the issue still appears in a scan of a current branch.

Language coverage

ZeroPath recognizes Python, JavaScript and TypeScript, Java, Go, Ruby, PHP, C and C++, C#, Rust, Swift and Objective-C, Kotlin, Scala, Dart, Elixir, Nim, AL (Business Central), and ObjectScript (InterSystems IRIS). Available analysis varies by language and scan mode.

Vulnerability Categories