Choose your platform, install Rootform, then verify the executable. Embedded Dialects are included and need no additional Rootform configuration for your first architecture.
Check provider coverage for interpreted types, provider bindings and input limits before choosing a runtime.
macOS
Recommended
curl -fsSL https://rootform.dev/install | shVerify
rootform versionOther options
Homebrew:
brew install rootform-dev/tap/rootformLinux
Recommended
curl -fsSL https://rootform.dev/install | shVerify
rootform versionWindows
Recommended
Invoke-RestMethod https://rootform.dev/install.ps1 | Invoke-ExpressionVerify
rootform versionContainer
Recommended
docker pull ghcr.io/rootform-dev/rootform:0.2.0Verify
docker run --rm ghcr.io/rootform-dev/rootform:0.2.0 rootform versionUse a release archive when you need exact binary bytes, checksum evidence, or a
transfer to a machine without network access. From
Rootform releases, select a
published product version and take its platform archive and SHA256SUMS.
The filenames below show archive conventions; use the selected release's
version in each name. A verification runtime is for contributor checks and does not
provide a product installation.
Release archives include binary license and third-party notices. Match the
archive against its SHA256SUMS entry before extraction:
shasum -a 256 rootform_0.2.0_darwin_arm64.tar.gzsha256sum rootform_0.2.0_linux_amd64.tar.gzGet-FileHash .\rootform_0.2.0_windows_amd64.zip -Algorithm SHA256Extract the .tar.gz or .zip, then place rootform or rootform.exe in
a directory on PATH. Run rootform version to confirm the executable.
To run a container, pin the image by index digest instead of using an archive. See Container usage. For a disconnected project, prepare exact third-party Dialects and Policy Packs as described in Locks and vendored content.
Update package-managed installations with their package managers:
- Homebrew:
brew upgrade rootform-dev/tap/rootform - Shell installer: run the recommended install command again. It replaces the executable in the same installation directory.
- Manual archive: replace the executable with the binary from the new release,
then verify it with
rootform version. - Container: pull the selected release tag again, for example
docker pull ghcr.io/rootform-dev/rootform:0.2.0.
Remove package-managed installations with:
- Homebrew:
brew uninstall rootform-dev/tap/rootform - Shell installer: remove
~/.local/bin/rootformby default, or the file under the customROOTFORM_INSTALL_DIR. - Manual archive: remove
rootformorrootform.exefrom itsPATHdirectory. - Container:
docker image rm ghcr.io/rootform-dev/rootform:0.2.0.
These steps remove the executable or image. rootform uninstall removes
installed Dialects or Policy Packs from $ROOTFORM_HOME; it does not remove
the executable. See the uninstall command reference.
Continue with the quickstart to analyze a sample plan, or analyze your own plan or state right away.