[Static analysis (SAST)]

Snyk Code and Aevral, at a glance

Snyk Code scans first-party code for security vulnerabilities and suggests fixes, inside the Snyk platform.

Snyk Code is built to find security vulnerabilities in first-party code and suggest the fix, inside the Snyk platform alongside dependency and container scanning. Aevral is built for a different reading of the same repository: authorization, IDOR, and business-logic access control, file by file with cross-file context. Vulnerability scanning and access-control reading are different jobs, so the two run in parallel.

Snyk Code focuses on

Finding security vulnerabilities in first-party code.
Suggesting fixes for what it finds.
Sitting in the Snyk platform with dependency and container scanning.

Aevral adds alongside

The reading of who has access to what: whether a change drops an ownership check, widens a role, or hands an object reference to the caller.
The business-logic reading: rules that stop being enforced server-side even while the code keeps working.
A finding as a lead with evidence for every claim, so a human can decide quickly.

Run them together

Let Snyk Code find the vulnerabilities and suggest fixes; let Aevral read who has access to what across the repository.

Snyk Code and Aevral, in depth; Aevral whole-repo scan.

Also alongside

Scan your whole repo for access bugs.

One GitHub App. A report with evidence. A prompt for the agent you already use.

Join waitlist