Install echidna with Homebrew, Nix

Project links

• Homepage
• Repository
• Upstream docs
• Package manager page

Commands and aliases

• echidna

Project history

The public GitHub repository was created in August 2017. The README describes Echidna as a Haskell program for fuzzing and property-based testing of Ethereum smart contracts, using grammar-based campaigns based on a contract ABI to falsify user-defined predicates or Solidity assertions.

Early public GitHub release artifacts date to 2018, with 1.0.0.0 published in June 2019. By 2026 the project had reached the 2.3.x release line and remained active, with thousands of GitHub stars and ongoing pushes.

The project grew from simple echidna_ boolean properties into a broader testing tool. The README documents property, assertion, Foundry, overflow, optimization, and exploration modes, corpus collection, coverage output, JSON output, shrinking/minimization, and line-level coverage reporting.

Echidna is part of the Crytic security tooling ecosystem. The README notes Slither integration for extracting useful information before fuzzing and crytic-compile support for Foundry, Hardhat, and Truffle projects.

Adoption history

Echidna's adoption followed smart-contract security practice: auditors and protocol developers needed fuzzing that understood Ethereum ABIs, Solidity assertions, build systems, and reproducible counterexamples. Its official docs live under the Building Secure Contracts material, placing it inside Trail of Bits/Crytic security education rather than only as a standalone CLI.

Distribution broadened beyond source builds. The README documents precompiled Linux and macOS binaries, Homebrew installation, Docker images hosted under the Crytic GitHub packages, and a GitHub Actions workflow through crytic/echidna-action. Homebrew installs Echidna with dependencies such as Slither and crytic-compile.

How it is used

Typical usage is to run echidna against a Solidity contract or project, define properties as echidna_-prefixed boolean functions, and let the fuzzer search for call sequences that falsify them. For modern projects, echidna . can use the current build framework through crytic-compile.

Configuration is commonly supplied through a YAML file passed with --config config.yaml. Users tune EVM and test-generation parameters, select test modes, collect corpora, and integrate results into text, JSON, or CI workflows.

Why package nerds care

Echidna is a good example of a specialized security CLI that packaging makes practical: the value is not a library import, but a reproducible executable with native dependencies, Solidity tooling, Slither, crytic-compile, solc management, and CI/container options all lined up.

It also shows the package-manager pressure created by blockchain tooling. Auditors want pinned versions for repeatable findings, while protocol teams want easy local installs and GitHub Actions coverage in fast-moving Solidity/Foundry/Hardhat projects.

Timeline

• 2017: Public Echidna repository created.
• 2018: Early GitHub release artifacts published.
• 2019: Echidna 1.0.0.0 released.
• 2020: Echidna 1.3.0.0 release line visible on GitHub.
• 2026: Echidna 2.3.2 released, with active repository maintenance.

Related projects

• Slither and crytic-compile are direct companion tools in the Crytic ecosystem.
• Foundry, Hardhat, and Truffle are supported build-system inputs.
• crytic/echidna-action and the official Docker images support CI and containerized adoption.

Sources

• https://github.com/crytic/echidna
• https://raw.githubusercontent.com/crytic/echidna/master/README.md
• https://secure-contracts.com/program-analysis/echidna/index.html
• https://secure-contracts.com/program-analysis/echidna/configuration.html
• https://github.com/crytic/echidna/releases
• https://api.github.com/repos/crytic/echidna
• https://github.com/crytic/echidna-action