What it is

A single-file Leo analyzer built on the shared ZK analyze layout. It renders a Monaco-based editor, runs compile-and-analyze, lists findings, and links to the full ZK Studio. The Supported Checks panel lists the detectors that run against Leo input.

Why it exists

Aleo / Leo programs manage private state via records and transitions; the common failure modes are record-privacy leaks and unused inputs. This page gives those checks a dedicated entry point for a single file.

Who uses it

Leo author — checks a transition before deploying.
Auditor — reviews a Leo file from an audit engagement.

How to open it

Sidebar → Library → Leo (Aleo).
/library → Leo (Aleo) card.
Direct URL — /leo-analyze.

Using the page

Editor — paste or type Leo source.
Analyze — findings populate below.
Launch ZK Studio — opens /zk-studio?lang=leo.
Supported Checks — lists the two detectors that run against the file:

Severity Detector

High Record Privacy Leaks

Medium Unused Inputs

Inputs and outputs

Input	Source	Required
Leo source	Editor	yes

Output	Format	Destination
Findings	In-page list	Editor section

Controls reference

Editor — Monaco editor with Leo syntax highlighting.
Launch ZK Studio — opens the full studio at /zk-studio?lang=leo.

Limits

Requires a signed-in account.
Single-file only. Multi-file projects need ZK Studio.

Troubleshooting

Symptom or error	Cause	Action
“Compile error”	Leo source fails to compile	Fix syntax and retry.
No findings on a known issue	Issue is outside the two supported checks	Open the file in ZK Studio.

ZK Studio — full IDE for Noir, Circom, Leo, and Cairo.
Noir Circuit Analysis — primary ZK entry point.
Cairo Analysis — StarkNet equivalent.

Severity	Detector
High	Record Privacy Leaks
Medium	Unused Inputs