entry-point-analyzer

You can identify state-changing entry points in a smart contract by automating attack surface mapping to detect externally callable functions that modify contract state. The process categorizes these functions by access level and generates detailed markdown reports for security audits.

The best way to map a smart contract attack surface is to automate the detection of externally callable state-changing functions. This approach categorizes entry points by access level—such as public, role-restricted, or contract-only—to provide an immediate overview of the audit scope.

Yes, the entry point analyzer supports Vyper and Rust smart contracts, along with Move, TON, and CosmWasm. It identifies and classifies state-changing entry points across these multiple languages to streamline security audits.

Yes, you can filter smart contract entry point analysis by specifying a target directory. This allows you to focus the detection of state-changing functions and access control classification on specific parts of the codebase.

Access classification for state-changing functions works by categorizing identified entry points into distinct access levels: Public, Role-Restricted, Contract-Only, and Review Required. This classification is generated within detailed markdown reports to highlight critical attack vectors.

Yes, smart contract entry point detection integrates with Slither for Solidity analysis. This integration helps automate the identification of state-changing functions and streamlines the overall security audit process.