entry-point-analyzer

To map state-changing entry points for a security audit, scan your contract repository to identify externally callable functions that modify state, while excluding read-only logic. This produces a structured markdown report detailing the attack surface.

Yes, the entry point analyzer supports Vyper and Solana/Rust contracts, alongside Solidity, Move, TON, and CosmWasm. It identifies external entry points, privileged operations, and access control patterns across these languages.

During smart contract analysis, access control patterns are conservatively classified into public, role-restricted, restricted, and contract-only categories. This classification is based on function visibility, modifiers, and caller checks.

Yes, you can exclude view and pure functions when scanning external entry points. The analysis specifically detects and filters out read-only and query handlers to focus entirely on state-changing logic.

The best way to document a smart contract attack surface for audit workflows is to generate a structured markdown report. This report includes function locations, detected restrictions, and a summary table of all state-changing entry points.

You should review trust-boundary callbacks when analyzing external entry points because they often invoke privileged operations that can alter contract state. Identifying these callbacks is crucial for accurate access classification and attack-surface mapping.