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.
Access control and logic flaws scanners miss
The flaws that depend on who may do what, which pattern matching cannot see.
Secrets and data exposure
Credentials and personal data that end up in code, logs or responses.
Dependencies (SCA)
Packages with known flaws, and malicious ones, checked when a lockfile changes.
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.
Containers and Kubernetes
Images and manifests that hand out more than they should.
Cloud configuration
Roles and services set up with more reach than the workload needs.
CI/CD pipelines
The workflows that build and ship your code.
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
Infrastructure and config
CI pipelines
Dependencies
When a turn changes a lockfile, LeoTrace checks the packages it brings in for known flaws and for malicious ones.
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