Onam

Which findings in this scan are real, and which only look suspicious?

SAST that separates the issues it can prove from the ones a person should review.

Onam's own static analysis engine runs data-flow, code-structure and reviewed pattern rules over your source, then splits the result: security issues it can show, and hotspots a person needs to confirm. Secret detection runs in the same pass.

source code
SAST
dependencies
SCA + SBOM
templates
IaC
running apps
DAST
Why this matters

A pattern rule flags every call to eval, every string that looks like SQL, every file that mentions a password.

Some of those are real. Most are not, and the scanner cannot tell which, so it calls all of them high. The developer opens the report, sees the noise, and closes it. The one finding that was a genuine injection path, from a request parameter to a database query, gets closed with the rest.

When every match is an alert

A scanner that gives a regex hit the same severity as a proven injection teaches the team to ignore both. What helps is being honest about what each rule can prove.

Severity follows evidence
How it works

How Static Analysis (SAST) works

  1. 01

    The scanner makes a shallow clone of the branch you chose and skips what is not your code: dependency and vendor folders, build output, minified files and anything over half a megabyte.

  2. 02

    Files are routed by extension. Python, JavaScript, TypeScript, Java, C#, Go, C, C++ and Ruby go to Onam's own static analysis engine; Terraform, YAML, JSON and Dockerfiles go to the IaC checker in the same job. GitHub Actions workflows, Terraform, npm config and HTML templates also get Onam's static analysis rules.

  3. 03

    Three kinds of rule run together, all written by Onam; no third-party rule packs are used. Data-flow rules follow untrusted input to a dangerous call within a single function, in Python, JavaScript/TypeScript, Java, C#, Go and Ruby. Code-structure rules match the shape of the code rather than its text, in all nine languages. Reviewed pattern rules add breadth, and each one has been triaged by hand. Rules judged to be about code quality or accessibility are dropped.

  4. 04

    Severity follows evidence. Data-flow and code-structure findings keep the severity their rule asserts. A pattern match is capped at medium, or low if its rule has not been reviewed, and is listed as a hotspot rather than a security issue. Several pattern rules firing on the same line are collapsed into one.

  5. 05

    Secret detection runs in the same pass, with Onam's own patterns for cloud keys, private-key blocks, GitHub, Slack and Stripe tokens, Google credentials, hard-coded JWTs and generic secret assignments.

  6. 06

    Each finding is stored with its file, line, rule, message, CWE, OWASP category, confidence and a short code snippet, and appears in the scan view, the project view and the platform-wide alerts list.

What you get

What you see in the console

Two lists
security issues you can act on now, and hotspots to review when you have time
Severity you can trust
pattern matches can never be rated high or critical
Data-flow rules where they matter most
Python, JavaScript/TypeScript, Java, C#, Go and Ruby, traced within each function
CWE and OWASP mapping
on every finding where the rule records them
Secrets in the same scan
cloud keys, private keys, SaaS tokens and hard-coded credentials
Less noise by design
vendored code, build output and minified files are not scanned
Rule guidance per finding
what the issue is, why it matters and a safe example
An AI fix prompt per finding
copy it into the assistant your team already uses
Fix branches on request
AI Code Fix rewrites flagged files onto a separate branch
The flow, in one picture

How Static Analysis (SAST) fits together

Three kinds of Onam rule (data-flow, code-structure and reviewed pattern rules) produce two lists: security issues and hotspots to review
Three kinds of rule, two kinds of result. Only rules that can show a flaw produce a security issue.
Illustrative layout of a code scan result: summary tiles, a security findings table and a finding detail with a copyable AI fix prompt
Illustrative: a stylised view of a scan result, not a screenshot. Names and findings are invented.
FAQ

Questions we get a lot

Python, JavaScript, TypeScript, Java, C#, Go, C, C++ and Ruby. Python, JavaScript/TypeScript, Java, C#, Go and Ruby have data-flow rules as well as code-structure rules; data flow is traced within a single function, not across functions. C and C++ have code-structure and pattern rules but no data-flow rules, so more of their results land in the hotspot list. Other languages, such as PHP, Kotlin, Rust, Swift and Scala, are not analysed today.
Next step

See Static Analysis (SAST) on your code

Give us a repository and we will scan it with you, then go through the security issues and the hotspots together.