cairo-vulnerability-scanner

To scan Cairo smart contracts for security vulnerabilities, run the automated scanner on your source directory to analyze contract logic and detect critical StarkNet risks like arithmetic overflows and storage collisions.

An automated StarkNet vulnerability audit detects six critical patterns including unchecked arithmetic, storage collisions, L1-L2 messaging flaws, and signature replay attacks by analyzing contract source code and L1 handler logic.

You need to run a StarkNet security audit during pre-launch assessments to identify and patch infinite mint vulnerabilities or signature replay risks before deploying your Cairo contracts to mainnet.

Yes, the Cairo vulnerability scanner requires static analysis integration to validate storage access, address boundaries, and cryptographic implementation when ensuring compliance with StarkNet security standards.

Yes, you can get actionable code fixes for L1-L2 messaging errors because the security reporting provides detailed findings with file references, severity levels, and recommended code fixes for your Cairo contracts.

Yes, you need the caracal dependency installed to check for arithmetic overflows in Cairo, as it provides the required integration for the scanner to analyze contract source code and L1 handler logic.