entry-point-analyzer

Identifying state-changing entry points involves mapping external calls and categorizing access patterns like Public or Role-Restricted. This focuses the security audit on potential state mutations by excluding read-only functions from the review.

Yes, smart contract entry point analysis works with Vyper, Solana, Move, TON, and CosmWasm projects, as well as Solidity. It detects language-specific entry points to map external calls across different blockchain platforms.

Yes, you can use Slither to auto-extract Solidity state-changing functions for access control reviews. If Slither is unavailable, the analysis falls back to manual extraction using language references to classify access patterns.

The best way to classify access patterns for external calls is to categorize them as Public, Role-Restricted, or Contract-Only. This classification highlights unrestricted and privileged state-changing functions for security reviews.

You generate a structured audit report by enumerating and classifying all externally callable state-changing functions in the codebase. The output markdown report categorizes access patterns to guide remediation and governance.

You should exclude read-only functions when mapping smart contract entry points because they cannot mutate contract state. Focusing on state-changing functions reduces manual surface-area mapping and highlights high-risk external calls.