entry-point-analyzer

To identify state-changing entry points for a security audit, analyze the codebase to detect externally callable functions that modify state, categorize them by access level, and exclude read-only operations. This maps the attack surface for deeper inspection.

Yes, you can find externally callable functions across multiple blockchain languages. The analyzer supports Solidity, Vyper, Solana/Rust, Move, TON, and CosmWasm codebases to detect functions that alter contract state.

You map the attack surface by classifying state-changing functions by access level, such as Public, Role-Restricted, or Contract-Only. This categorization highlights potential privilege escalation vectors during security audits.

View and pure functions are excluded from attack surface analysis because they are read-only operations that do not modify contract state. The analysis focuses strictly on state-changing entry points that present actual security risks.

The best way to start a smart contract security audit is to generate a structured report of all state-changing entry points. This allows you to quickly identify and prioritize externally callable functions that can alter the contract state.

Yes, entry-point-analyzer works with CosmWasm and Move codebases. It analyzes these codebases alongside Solidity, Vyper, Solana/Rust, and TON to detect state-changing functions and generate structured audit reports.