Cairo (StarkNet) Analysis is the quick way to check a single Cairo file. You paste or type the source into an in-page editor, run the analysis, and read the findings below — a fast, single-file check ahead of the full studio.
Why it exists
Cairo has arithmetic-specific failure modes that don’t depend on on-chain semantics — felt overflow and missing assertions chief among them, where a value wraps or an unchecked path slips through. This page surfaces those checks as a single-file workflow you can run before deploying to StarkNet.
Who uses it
- Cairo author — checks a program before deploying to StarkNet.
- Auditor — reviews a Cairo file from an engagement.
How to open it
- From the Library → Cairo (StarkNet).
- Direct URL —
/cairo-analyze.
Using the page
Type or paste Cairo 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 Cairo file:
| Severity | Check |
|---|---|
| High | Felt overflow |
| Medium | Missing assertions |
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.
- Leo (Aleo) Program Analysis — the Aleo equivalent.
- Noir Circuit Analysis — the primary ZK entry point.