OpenViSTAI · Agents · Blockchain · Crypto
Menu
Developer Tools

Foundry Toolchain

Foundry Toolchain is a GitHub Actions component that installs the Foundry toolkit in CI workflows for Ethereum development projects, allowing subsequent job steps to run Forge commands.

Independent OpenViST project profile, based on linked sources.

Foundry Toolchain — OpenViST project profile in Developer Tools.
OpenViST project illustration. See the linked sources for product details.
Understand the project

Practical overview

When it fits

Use it as an installation step in a GitHub Actions workflow when later CI steps need Foundry commands.

Who it is for

  • Ethereum developers maintaining GitHub Actions workflows for Foundry projects.
  • Teams that want CI jobs to install Foundry before running Forge checks.

Documented uses

  • Install a selected Foundry version in a GitHub Actions job.
  • Run Forge formatting checks, builds and tests after installation.
  • Configure whether Foundry data is cached and choose cache keys.
Before you choose

Requirements & limits

  • The version input defaults to stable and also accepts nightly or a SemVer version.
  • Caching defaults to enabled and can be disabled or customized with cache and restore keys.
  • The README warns that the described cache strategy requires a fuzz seed for fork tests that use fuzzing.

Check current requirements in the official documentation. Source-based guidance does not mean OpenViST has run or independently tested this project.

Source-based practical guide

Install Foundry and run Forge checks in GitHub Actions

Add Foundry installation to a CI workflow, then invoke Forge version, formatting, build and test commands.

Before you start

  • A GitHub Actions workflow for a Foundry project.
  • An Ubuntu runner, as shown in the example workflow.

Steps

  1. Check out the repository; the example checks out submodules recursively.

  2. Add foundry-rs/foundry-toolchain@v1 as an installation step.

  3. Add Forge steps such as forge --version, forge fmt --check, forge build --sizes and forge test -vvv.

Expected outcome

The workflow installs Foundry before running the listed Forge commands.

Guide limitations

  • The example shows workflow structure and commands; it does not configure checks for a specific project.
  • Caching is enabled by default. The README says fork tests that fuzz need a fuzz seed for the described cache strategy to work.
Evidence and transparency

Sources & review

Source record details
Source availability
Active
Sources checked
9 October 2026
Original website title
foundry-rs/foundry-toolchain · Official homepage title · retained in its source language