entry-point-analyzer

To identify state-changing entry points in smart contracts, you can run an entry-point analyzer on your repository. It maps externally callable functions across multi-language codebases and produces audit-ready reports that exclude read-only functions.

Classifying access control on externally callable functions is done by analyzing function signatures and modifiers across multi-language codebases. The process categorizes access patterns as Public, Role-Restricted, or Contract-Only to generate a structured audit report.

Yes, you can audit smart contracts written in multiple languages simultaneously. The analyzer applies its entry-point detection logic across multi-language codebases to map state-changing functions and return a unified per-file summary.

To exclude read-only functions when generating an audit report, the analyzer specifically filters for state-modifying entry points. It identifies externally callable functions that alter contract state and omits view or pure functions from the final structured output.

Yes, the entry-point analyzer works without external dependencies or components. It independently processes your smart contract repository to map callable functions, classify access control, and produce structured audit-ready reports.