Application TestingLiveFrom Builder ($69/mo)

SAST

Sift (Code analysis) traces security defects to the file and line without running your application. Scan a Git repository or paste code, choose a quick, standard or deep scan, and get AI fix guidance on each finding.

Detection Coverage

What SAST detects

SQL & Command Injection

User input traced to dangerous sinks: SQL queries, shell commands and file paths.

Cross-Site Scripting

Untrusted data reaching HTML output and JavaScript execution contexts.

Hardcoded Secrets

Credentials, API keys and private key material embedded in source code.

Insecure Deserialisation

Unsafe deserialisation of untrusted data.

Path Traversal

User-controlled file paths that escape the intended directory.

Access Control and Auth

Missing authorisation checks and insecure authentication patterns.

Cryptographic Weaknesses

Weak algorithms such as MD5, SHA-1 and DES, and insecure random number generation.

Custom Rules

Up to 50 organisation-specific regex rules alongside the built-in rules. On Pro and above.

How it works

From repository to findings

  1. 1

    Choose your source

    Give a repository URL and branch on GitHub, GitLab, Bitbucket or Azure DevOps, or paste code directly.

  2. 2

    Language detection

    Repository scans detect the languages in use. Pasted code supports JavaScript, TypeScript, Python, Java, Go, Ruby, PHP and C#.

  3. 3

    Rules and data flow

    Scans apply the rule set written for each file's language. OWASP Top 10 and CWE Top 25 rule sets can be added or chosen on their own.

  4. 4

    Findings with AI fix

    Each finding shows the file, line, CWE and code snippet. An AI review flags likely false positives, and AI fix guidance is available per finding.

app/routes/user.jsJavaScript
// Line 42 - tainted user input reaches SQL sink
const userId = req.query.id;          // source
const q = `SELECT * FROM users
           WHERE id = ${userId}`;     // sink
await db.query(q);
FindingExample finding: SQL injection via an unsanitised query parameter. Use parameterised queries. CWE-89 · OWASP A03

Spoorder SAST vs a pattern-only scanner

CriterionSpoordera pattern-only scanner
AnalysisPattern rules plus cross-file data flowSingle-file pattern matching
False positivesAI review flags likely false positivesManual triage
RemediationAI fix guidance per findingDocumentation link only
Compliance mappingFindings mapped to framework controlsSeparate manual step
What happens to my source code?

For a repository scan, Spoorder clones the repository into a temporary directory, scans it and deletes the clone when the scan finishes. Pasted code travels with the scan job and is not stored. Findings keep the file path, line number and a short code snippet.

How does taint analysis reduce false positives?

Taint analysis traces untrusted data from its source, such as an HTTP parameter, to a dangerous sink, such as a SQL query. Only paths where untrusted data reaches a sink without sanitisation are flagged, which produces fewer false positives than pattern matching alone.

Can SAST block a pull request?

A pipeline step can evaluate a security gate against a completed scan with an API key that has the scan scope, and a blocking gate that fails answers HTTP 422, which fails the step. The CI/CD docs have the requests.

Which languages are supported?

Pasted code supports JavaScript, TypeScript, Python, Java, Go, Ruby, PHP and C#. Repository scans detect the languages in the repository and apply the matching rulesets.

What plan do I need for SAST?

SAST is included from the Builder plan ($69/mo). A SAST scan costs 5 credits.

Can I write custom SAST rules?

Yes, on Pro and above. In Settings you can define up to 50 regex-based custom rules per organisation. Builder includes SAST with the built-in rules only.

Start scanning

Start with a free health check. SAST is included from Builder ($69/mo).