Installer crytic-compile avec Homebrew

Liens du projet

• Page d'accueil

Commandes et alias

• crytic-compile

Historique du projet

The official README presents crytic-compile as a library for smart contract compilation, with support for direct solc compilation and framework-specific projects including Foundry, Hardhat, Brownie, Truffle, Waffle, Dapp, Embark, Etherlime, Sourcify, and Etherscan-style sources.

Historique d'adoption

The README says the plugin is used in Trail of Bits tools including Slither, Echidna, Manticore, and evm-cfg-builder. That places crytic-compile in the packaging path for Solidity security-analysis workflows rather than only as a standalone CLI.

Modes d'utilisation

The documented CLI workflow is to run crytic-compile at a project root, for example beside hardhat.config.js or foundry.toml, and produce crytic-export/contracts.json containing AST, ABI, and bytecode data. Advanced options are supplied as CLI flags or library arguments, not through a documented standalone config file.

Pourquoi les passionnés de paquets s'y intéressent

For package managers, crytic-compile is a Python security tool whose value depends on integration with external build frameworks and Solidity compiler tooling. Its distribution via PyPI and Homebrew makes it convenient to install as part of audit and fuzzing toolchains.

Chronologie

• 2019: PyPI release 0.1.0 was uploaded.
• 2026: Release 0.4.1 is current in PyPI and Homebrew metadata.

Related projects

• The official README names Slither, Echidna, Manticore, and evm-cfg-builder as Trail of Bits tools that use crytic-compile.

Sources

• https://github.com/crytic/crytic-compile#readme
• https://github.com/crytic/crytic-compile/wiki/Configuration
• https://pypi.org/pypi/crytic-compile/json
• https://formulae.brew.sh/formula/crytic-compile