macOS
Homebrewverified · 100%
brew install crytic-compileprovider-native install command
brew / rank 2250
Install crytic-compile with Homebrew
Abstraction layer for smart contract build systems. Version 0.4.2 via Homebrew; verified 2026-07-30.
install
Additional install commands
overview
Package summary
Abstraction layer for smart contract build systems
Project links
Commands and aliases
- crytic-compile
history
Project history and usage
crytic-compile is a smart-contract compilation abstraction layer from the Crytic ecosystem. It matters to package users because it normalizes many Ethereum project build systems behind one CLI and Python library interface.
Project history
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.
Adoption history
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.
How it is used
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.
Why package nerds care
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.
Timeline
- 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
security posture
Risk level: yellow
generalized runtime or code generation signal.
Risk classifier
yellow risk · medium confidence · runtime
Why
- generalized runtime or code generation signal
Signals
- text:build system
Install behavior
- No Homebrew bottle metadata was recorded.
Recommended review
Before unattended agent use, check whether the tool reads plaintext credentials, writes remote state, publishes artifacts, or shells out to plugins.
executables
Installed executables
| Command | Kind | Exposure | Note |
|---|---|---|---|
crytic-compile | executable | indexed executable | Discovered from the local executable index. |
freshness
Version and freshness
These signals separate page generation age, package-manager activity, and upstream release comparison. Version lag is warned only when an evidence URL and comparable versions are present.
page generated2026-08-03
manager version0.4.2
manager updated2026-07-30
local dataunknown
upstreamnot available
latest detectednot detected
- okNo freshness warnings were generated.
install metadata
Package metadata
| Package key | brew:crytic-compile |
|---|---|
| Version | 0.4.2 |
| Package manager | Homebrew |
| Homepage | https://github.com/crytic/crytic-compile |
| Repository | https://github.com/crytic/crytic-compile |
| Last updated | 2026-07-30T01:26:44Z |
| Pulse | updated |
| Bottle | not recorded |
| Service | none declared |
source trail
Generated from repository data
This page is generated by av-web from the private package SQLite artifact built by scripts/generate-pkg-sqlite.py.
Combined YAML source
View the package source record on GitHub.
Used sources
- Geiger risk classifier
- Nucleus package database
- curated package history
- pkgdb category and tag curation