x-ray

A smart contract pre-audit briefing combines code-scoped architecture, entry-point mapping, threat model guidance, and git-history security observations into a structured report. It helps auditors and security researchers quickly identify where to focus before running deeper analysis.

You can map smart contract entry points by running an automated analysis tool that classifies call structures and generates an entry-point map. This helps identify external attack surfaces and builds a threat model by evaluating trust boundaries within the protocol's architecture.

Yes, pre-audit analysis works with Foundry and Hardhat repositories. The tool detects the project root and source directories, enumerates nSLOC and tests, and optionally attempts coverage if the Foundry or Node toolchain is available in the environment.

You need python3, bash, curl, grep, find, and git installed to run git security analysis and test coverage checks. Node and Foundry are optional dependencies required only if you want the tool to attempt automated test coverage generation.

The best way to identify security hotspots is to run git-history security analysis combined with test presence scanning. This approach highlights security-relevant code evolution and areas lacking test coverage, directing auditors to high-risk sections before deep analysis.

Automated pre-audit protocol reports are limited to providing a rapid briefing rather than a comprehensive security audit. They rely on detecting project structures and available toolchains, meaning coverage attempts and git security analysis may be skipped if optional dependencies like Foundry or Node are missing.