Code scanning
Elliot runs Elliot-1, our offensive security model, against your repository on every push and reports only the vulnerabilities it can trace from input to impact. Each one comes with the request that triggers it, a proof of concept and the fix.
Run a free scanEvery finding shows its work.
Open a finding and follow the attacker’s path through your code, step by step, with real files and line numbers. Below it: who can reach the bug, the request that triggers it and the change that fixes it.
What happens in a scan.
Elliot works through your repository in five passes. Findings stream onto your board while the scan is still running.
- 01
Index
Maps routes, handlers, callers and deploy config at the head of your branch.
- 02
Threat model
Works out what is worth stealing, where the trust boundaries are and how tenants are kept apart.
- 03
Hunt
Attacks every entry point from several angles, and digs again wherever it finds something.
- 04
Ground
Checks each step of every trace against your real code and merges reports that share a root cause.
- 05
Prove reach
Decides who can reach the bug and what they gain. If the answer is nothing, it stays off your board.
What each finding includes
The exploit trace
Source, via and sink: each step a file and line in your code, checked against the code before the finding is published.
How an attacker gets there
Who can reach the bug, with what privilege, and the request that triggers it.
A proof of concept
Elliot writes one for each finding and runs it against your code in an isolated sandbox.
The fix
What to change in your code, with the diff. Your coding agent can pick it up through Elliot’s MCP server.
Severity and confidence
Severity, CWE, Elliot’s confidence and how many independent agent reports back the finding.
A place on your board
Triage, to do, in progress, in review, fixed. Mark it fixed and the next scan checks for it again.
Start with a free scan.
Connect GitHub, pick a repository and run a full scan for free. You see up to five findings in full, with the trace, the request and the fix. Choose a plan and the same scan carries on past them.
Free
$0
- 1 repository
- One full scan, up to five findings
- Each finding in full, with trace, request and fix
- Daily supply chain analysis
- Upgrade and the scan carries on
- Model: Elliot-1
Pro
$149per month
- 2 repositories
- 200 scans a month
- Then $1 per extra scan
- Up to 10 contributors
- Full findings with trace, request and fix
- Daily supply chain analysis
- Model: Elliot-1
Team
$499per month
- 10 repositories
- 1,000 scans a month
- Then $1 per extra scan
- Up to 25 contributors
- Full findings with trace, request and fix
- Daily supply chain analysis
- Model: Elliot-1
Enterprise
Custom
- Unlimited repositories
- Scan volume to match
- SAML single sign-on
- Audit logging
- Dedicated support channels
- Daily supply chain analysis
- Model: Elliot-1
Questions.
What starts a scan?
A push to the branches you choose, a pull request, or Scan now in the dashboard. Incremental scans read the files that changed since the last completed scan.
Which languages does it read?
JavaScript and TypeScript, Python, Ruby, Elixir, Go, Rust, PHP, Java and Kotlin, and more. Elliot also reads CI and deploy config.
Does Elliot run my code?
Only inside a sandbox. To test a finding, Elliot writes a proof of concept and runs it against your code in an isolated sandbox. Your servers and deployments stay untouched.
See what Elliot finds in your code.
Connect GitHub, choose a repository and Elliot runs its first full scan for free.
Run a free scan