cairo-vulnerability-scanner

To audit Cairo smart contracts, you can scan source files in the src/*.cairo directory to detect critical vulnerability patterns like unchecked arithmetic, address handling, and replay protection, generating a structured report with severity and mitigations.

When auditing L1-L2 bridge implementations, check for six critical vulnerability patterns including unchecked arithmetic, unsafe address handling, missing replay protection, and flawed cross-layer messaging logic to prevent asset loss.

Static analysis detects replay protection flaws by scanning Cairo source files to identify missing or inadequate signature verification and cross-layer messaging patterns, reporting the exact file references and practical mitigations needed.

Yes, you can automate security auditing for StarkNet projects by scanning Cairo contracts to identify vulnerability patterns in cross-layer messaging and signature verification, producing a structured report with severity levels and recommended fixes.

The best way to perform threat modeling for Cairo contracts is running an automated vulnerability scanner that applies static analysis to identify critical patterns, providing workflow guidance for end-to-end verification across StarkNet projects.

Your Cairo contract audit may miss unchecked arithmetic vulnerabilities if the scanner lacks specific pattern detection for arithmetic safety; automated scanning of src/*.cairo files ensures these critical flaws are identified with actionable mitigations.