audit-prep-assistant

Codebase security audit preparation involves defining audit goals, running static analysis tools like Slither or golangci-lint, increasing test coverage, removing dead code, and generating documentation artifacts to present clear evidence to auditors.

An audit prep workflow for smart contracts includes establishing audit objectives, orchestrating static analysis with tools like Slither, expanding test coverage, triaging findings, and generating flowcharts and inline comments to support the audit narrative.

Yes, the audit prep process supports Rust and Go codebases by guiding and consolidating static analysis using dylint for Rust and golangci-lint for Go, alongside general test coverage and dead-code removal steps.

Removing dead code before a security review reduces the attack surface and clarifies the codebase logic, allowing auditors to focus on active risk areas and verify test coverage without triaging unused or irrelevant code paths.

Static analysis organizes a security audit by running linting tools to surface vulnerabilities and code inconsistencies, triaging the findings, and consolidating the results into a ready-to-review package for the assessment team.

Auditors need documentation artifacts like flowcharts, user stories, and inline comments that explain the codebase's intended behavior, which are generated during audit prep to support a clear and structured audit narrative.