entry-point-analyzer

To identify state-changing entry points for a security audit, you can analyze the codebase to detect functions that modify contract state, categorizing them by external callability and access control patterns while excluding read-only operations.

Mapping a smart contract attack surface involves systematically identifying all externally callable functions that alter state across supported languages like Solidity, Vyper, Solana, Move, TON, and CosmWasm to prioritize deeper inspection.

Yes, this smart contract analyzer supports access control analysis for Solidity and Vyper, as well as Solana, Move, TON, and CosmWasm, classifying functions by access level such as Public, Role-Restricted, and Contract-Only.

Analyzing external callability and state modification potential requires scanning the smart contract codebase to detect state-changing functions, leveraging tools like Slither when available to classify access control patterns.

Yes, you can leverage tools like Slither when available to detect state-changing functions and map the attack surface across multiple languages including CosmWasm and TON, categorizing entry points by access level.

Excluding read-only operations when mapping a smart contract attack surface is necessary because the analysis specifically targets state-changing entry points that can modify contract state, ensuring audit efforts prioritize actual vulnerability vectors.