Automic VaultAutomic Vault

brew

terramate mit Homebrew, Nix, winget installieren

Prüfe Installationswege, Executables, Metadaten und Sicherheitshinweise für terramate in AI-Agent-Workflows.

Installation

Weitere Installationsbefehle

macOS

Homebrewverifiziert · 100%
brew install terramate

local Homebrew formula metadata

Linux

Nixverifiziert · 92%
nix profile install nixpkgs#terramate

nixpkgs package indexes · pkgs/by-name/te/terramate/package.nix · Quelle: api.github.com

Windows

Windows Package Managerverifiziert · 92%
winget install --id Terramate.CLI -e

Windows Package Manager source index · Terramate.CLI · Quelle: cdn.winget.microsoft.com

Überblick

Paketzusammenfassung

Managing Terraform stacks with change detections and code generations

Befehle und Aliase

  • terramate-ls

Verlauf

Projektgeschichte und Nutzung

Terramate is an open-source Infrastructure as Code orchestration and code-generation CLI for Terraform, OpenTofu, Terragrunt, Kubernetes, and CI/CD workflows.

Projektgeschichte

The public Terramate repository was created in September 2021. Its README describes Terramate CLI as an open-source orchestration and code generation engine for scaling IaC, with optional pairing to Terramate Cloud for managed observability, drift detection, asset management, policy, and notification features.

Terramate's project model is built around stacks. The README emphasizes breaking large infrastructure into smaller stacks, reducing duplicated configuration through generated HCL, JSON, or YAML, and orchestrating commands across stacks with a graph-based engine.

The official CLI docs describe Terramate as a daily IaC workload tool for managing stacks, maintaining a DRY codebase with code generation, planning and deploying with orchestration and change detection, and synchronizing data with Terramate Cloud.

Adoptionsgeschichte

Terramate is newer than Terragrunt but has become a visible Terraform/OpenTofu orchestration package. Repository metadata showed several thousand stars by July 2026, and input package metadata lists Homebrew, Nix, and winget packages.

The README's onboarding claims are aimed at incremental adoption: existing Terraform, OpenTofu, or Terragrunt projects can start with a single command and without refactoring, while teams can adopt features individually to avoid hard lock-in.

Wie es verwendet wird

Common CLI usage includes creating and listing stacks, running commands such as terraform init or terraform apply across all or changed stacks, generating repeated backend and provider configuration, and filtering execution by Git changes, tags, directories, or Terramate Cloud status.

The official change-detection docs explain the --changed workflow for running commands only in stacks affected by a commit, branch, or pull request. The code-generation docs describe generating stack files from blueprints to keep Terraform backend and provider configuration DRY.

Warum Paket-Nerds sich dafür interessieren

For package-manager users, Terramate is significant because it packages a higher-level IaC workflow engine as a single CLI. It is useful in dev shells and CI images where users already install Terraform, OpenTofu, or Terragrunt and want change detection, orchestration, and generated configuration without adopting a hosted CI product.

Its cross-platform package metadata, Go-based install path, and optional Cloud pairing make it both a local CLI package and an entry point into a larger IaC platform.

Zeitleiste

  • 2021: Public Terramate repository created.
  • 2020s: CLI docs establish stack management, code generation, orchestration, and change detection as core workflows.
  • 2026: Homebrew, Nix, and winget metadata list Terramate CLI packages.

Related projects

  • Terraform and OpenTofu are primary IaC engines Terramate orchestrates.
  • Terragrunt is explicitly supported as an existing project style that Terramate can onboard.
  • Terramate Cloud is the optional managed service paired with the open-source CLI.

Quellen

  • CLI reference: https://terramate.io/docs/cli/reference/cmdline/
  • Change detection docs: https://terramate.io/docs/cli/change-detection/
  • Code generation docs: https://terramate.io/docs/cli/code-generation/
  • Docs: https://terramate.io/docs
  • Input package metadata: source_facts.package-manager
  • README: https://github.com/terramate-io/terramate#readme
  • Repository metadata: https://api.github.com/repos/terramate-io/terramate

Sicherheitslage

Risikostufe: grün

narrow executable package without higher-risk signals.

Risikoklassifikator

grün Risiko · niedrig Konfidenz · appliance

Warum

  • narrow executable package without higher-risk signals

Signale

  • metadata:no-higher-risk-signals

Installationsverhalten

  • In den Formelmetadaten ist kein Homebrew-Post-install-Hook erfasst.
  • Homebrew-Bottle-Metadaten sind für 6 Plattformziele verfügbar.
  • Build-Metadaten listen 1 Build-Abhängigkeiten.

Empfohlene Prüfung

Prüfe vor unbeaufsichtigter Agent-Nutzung, ob das Tool Klartext-Credentials liest, Remote-Zustand schreibt, Artefakte veröffentlicht oder Plugins ausführt.

local files

Configuration and credential file locations

These source-backed paths show where this package keeps local settings or durable credentials. Automic Vault can use them as review targets for secret scanning, migration, and command approval.

Configuration files

Config paths the tool may read or write during local use.

Unix
<project>/**/*.tm.hcl<project>/**/*.tm

Executables

Installierte Executables

BefehlArtSichtbarkeitHinweis
terramate-lscliglobales Executable

Aktualität

Version und Aktualität

Diese Signale trennen das Alter der Seitengenerierung, Aktivität des Paketmanagers und Upstream-Release-Vergleich. Versionsrückstand wird nur gemeldet, wenn eine Evidenz-URL und vergleichbare Versionen vorhanden sind.

Seite generiert2026-07-26
Manager-Version0.17.1
Manager aktualisiert2026-05-26
lokale DatenOK
Upstreamaktuell
neueste erkannte Versionv0.17.1

https://github.com/terramate-io/terramate

  • OKEs wurden keine Aktualitätswarnungen generiert.

Installationsmetadaten

Paketmetadaten

Paketschlüsselbrew:terramate
Version0.17.1
PaketmanagerHomebrew
Paketmanager-Seitehttps://formulae.brew.sh/formula/terramate
Homepagehttps://terramate.io/docs/
Repositoryhttps://github.com/terramate-io/terramate
Upstream-Dokumentationhttps://terramate.io/docs
LizenzMPL-2.0
Quellarchivhttps://github.com/terramate-io/terramate/archive/refs/tags/v0.17.1.tar.gz
Zuletzt aktualisiert2026-05-26T16:51:44Z
Pulseupdated
Build-Abhängigkeitengo
Bottleverfügbar (auf arm64_linux, arm64_sequoia, arm64_sonoma, arm64_tahoe, sonoma, x86_64_linux)
Homebrew post-installnicht definiert
Dienstkeiner deklariert

Registry-Fakten

Details aus der Quelldatenbank

Source DatabaseHomebrew formula API
Taphomebrew/core
Full Nameterramate
Version Scheme0
Revision0
Head VersionHEAD
Conflicts With
  • tenv
Bottle Stable Root URLhttps://ghcr.io/v2/homebrew/core
Deprecatedno
Disabledno
Keg Onlyno
URL Keys
  • head
  • stable

Source-Datenbank-Treffer

Andere Paketmanager-Einträge

Treffer stammen aus externen Paketmanager-Indizes und bleiben von lokalen Automic-Vault-Paketlinks getrennt.

Nix95%

terramate

nix profile install nixpkgs#terramate
  • normalized package name match
  • Abgeglichen nach: Terramate
nixpkgs package indexes · api.github.com · nixpkgs package indexes: pkgs/by-name/te/terramate/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1
winget95%

Terramate.CLI

winget install --id Terramate.CLI -e
  • normalized package name match
  • Abgeglichen nach: Terramate
Windows Package Manager source index · cdn.winget.microsoft.com · Windows Package Manager source index: Terramate.CLI from https://cdn.winget.microsoft.com/cache/source.msix

Quellspur

Aus Repository-Daten generiert

Diese Seite wird von av-web aus dem privaten Paket-SQLite-Artefakt bereitgestellt, das scripts/generate-pkg-sqlite.py erstellt.

Verwendete Quellen

  • Geiger risk classifier
  • Nucleus package database
  • av.db category and tag curation
  • cross-ecosystem install command graph
  • curated configuration and credential file locations
  • curated package history
  • external package-manager database matches
  • package relationship graph
  • package version freshness
  • package-page enrichment