entry-point-analyzer

To map the attack surface during a smart contract security audit, you can automatically parse external function signatures and access control patterns. This process categorizes state-changing functions into public, role-restricted, and contract-only groups.

The best way to map a DeFi protocol attack surface is to systematically detect all state-changing functions while excluding read-only view and pure functions. Generating a structured markdown report of these privileged operations highlights sensitive areas for manual review.

Yes, the smart contract entry point analyzer supports Vyper and Rust codebases, alongside Solidity, Move, and TON. It parses external function signatures across these languages to categorize state-changing functions by access level.

To classify access control levels for external functions in Solidity, you parse the codebase to identify modifiers and role restrictions. The analyzer categorizes these state-changing functions into public, role-restricted, and contract-only classifications.

You should exclude view and pure functions when auditing smart contract security because they cannot modify contract state. Focusing on state-changing entry points allows you to concentrate manual review efforts on privileged operations that present actual attack vectors.