What LeoTrace covers.
Far more than SAST.

Code, dependencies, infrastructure, containers and pipelines, each reviewed in the turn that changes them. The rules stay on our server.

More than SAST.
Where LeoTrace looks, with a few familiar examples.

Code flaws

Flaws in the code your agent writes, in every language it reads.

  • Injection
  • Server-side request forgery
  • Path traversal

Access control and logic flaws scanners miss

The flaws that depend on who may do what, which pattern matching cannot see.

  • Insecure direct object reference
  • Missing authorisation
  • Mass assignment

Secrets and data exposure

Credentials and personal data that end up in code, logs or responses.

  • Hardcoded secrets
  • Sensitive data in logs

Dependencies (SCA)

Packages with known flaws, and malicious ones, checked when a lockfile changes.

  • npm
  • Go

Data sources. Vulnerability data comes from OSV.dev, which brings together the GitHub Advisory Database and the Go Vulnerability Database (both CC BY 4.0) and OpenSSF Malicious Packages (Apache 2.0). LeoPrevent works out severities, fix versions and verdicts from this data, and each finding links to its OSV advisory. The original providers do not endorse LeoTrace.

Infrastructure as code

Terraform, CloudFormation and the rest, before they are applied.

  • Resources opened to anyone
  • Data stores without encryption

Containers and Kubernetes

Images and manifests that hand out more than they should.

  • Containers running as root
  • Privileged containers
  • Over-broad RBAC grants

Cloud configuration

Roles and services set up with more reach than the workload needs.

  • Over-broad IAM grants
  • Services reachable from the internet

CI/CD pipelines

The workflows that build and ship your code.

  • Workflow injection
  • Unpinned third-party actions

Need the full rule list for a security review? We share it with customers under NDA. Contact sales

The files a review reads.
Code, infrastructure and pipelines.

Rules written for any language apply to every code file; the rest apply to the languages they name. Prose and stylesheets are never reviewed, and secret files are never sent.

Code

  • Python
  • JavaScript
  • TypeScript
  • Java
  • PHP
  • Ruby
  • Go
  • C#
  • Rust
  • Kotlin
  • Scala
  • Swift
  • SQL
  • Shell
  • Lua
  • HTML

Infrastructure and config

  • Terraform and OpenTofu
  • HCL
  • Bicep
  • CloudFormation and SAM
  • Azure Resource Manager
  • Kubernetes, Helm and Kustomize
  • Dockerfile and Containerfile
  • YAML
  • JSON

CI pipelines

  • GitHub Actions
  • GitLab CI
  • CircleCI
  • Azure Pipelines
  • Bitbucket Pipelines
  • Buildkite

Dependencies

When a turn changes a lockfile, LeoTrace checks the packages it brings in for known flaws and for malicious ones.

  • npm
  • package-lock.json
  • npm-shrinkwrap.json
  • pnpm-lock.yaml
  • Go
  • go.mod
  • go.sum

Your agent’s security advisor, one prompt away.

  • Works in the coding agent you already use
  • Reviews start on your next turn
  • ISO 27001 certified
What should we cover?