Leo (Aleo) Program Analysis is the quick way to check a single Leo file. You paste or type the source into an in-page editor, run the analysis, and read the findings below — a dedicated check loop without opening the full studio.
Why it exists
Aleo programs manage private state through records and transitions, and their common failure modes are record-privacy leaks and unused inputs — mistakes that quietly weaken the privacy the program is supposed to provide. This page gives those checks a fast, single-file home.
Who uses it
- Leo author — checks a transition before deploying.
- Auditor — reviews a Leo file from an engagement.
How to open it
- From the Library → Leo (Aleo).
- Direct URL —
/leo-analyze.
Using the page
Type or paste Leo source into the editor and run the analysis; findings populate underneath. Launch ZK Studio opens the source in the full multi-file workspace. The Supported Checks panel lists what runs against a Leo file:
| Severity | Check |
|---|---|
| High | Record privacy leaks |
| Medium | Unused inputs |
Limits
- Requires a signed-in account; analysis runs in the browser on the pasted source.
- Single-file only — multi-file projects need ZK Studio.
- The findings cover the checks above; anything outside them may need the full studio analysis.
Related pages
- ZK Studio — the full IDE for Noir, Circom, Leo, and Cairo.
- Noir Circuit Analysis — the primary ZK entry point.
- Cairo (StarkNet) Analysis — the StarkNet equivalent.