entry point analyzer

Security Community

Skill notes

When to Use

Use this skill when: Starting a smart contract security audit to map the attack surface Asked to find entry points, external functions, or audit flows Analyzing access control patterns across a codebase Identifying privileged operations and role-restricted functions

When NOT to Use

Do NOT use this skill for: Vulnerability detection (use audit-context-building or domain-specific-audits) Writing exploit POCs (use solidity-poc-builder) Code quality or gas optimization analysis Non-smart-contract codebases

Scope: State-Changing Functions Only

This skill focuses exclusively on functions that can modify state. Excluded: Language · Excluded Patterns Solidity · view, pure functions Vyper · @view, @pure functions Solana · Functions without mut account references

Workflow

Detect Language - Identify contract language(s) from file extensions and syntax Use Tooling (if available) - For Solidity, check if Slither is available and use it Locate Contracts - Find all contract/module files (apply directory filter if specified) Extract Entry Points - Parse each file for externally callable, state-changing functions Classify Access - Categorize each function by access level

Slither Integration (Solidity)

For Solidity codebases, Slither can automatically extract entry points. Before manual analysis:

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
Security
Author-declared agents
No explicit declaration found; this is not inferred or tested compatibility
Static check
88 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
Author / version / license
@trailofbits · no license declared
Token usage
Lean
Setup complexity
Guided setup
External API key
Not required
Operating systems
Unspecified (assume cross-platform)
Runtime requirements
No explicit requirements detected
Detected file/system behavior
  • Read-only
  • Write / modify
  • Shell exec
Network behavior
Local-only
Install commands
None (reference only)

Heads up: Tool permissions are not declared; actual access depends on the runtime.

Output preview entry-point-analyzer.preview
# 3. Use Slither Output as Foundation

- Parse the Slither output table to populate your analysis
- Cross-reference with manual inspection for access control classification
- Slither may miss some patterns (callbacks, dynamic access control)—supplement with manual review
- If Slither fails (compilation errors, unsupported features), fall back to manual analysis

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.