# tfschema mit Homebrew installieren

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

## Installation

```sh
sudo av install brew:tfschema
```

Weitere Installationsbefehle:

### macOS

- Homebrew (100%):

```sh
brew install tfschema
```

  Evidenz: local Homebrew formula metadata

## Paketfakten

- **Paketschlüssel:** brew:tfschema
- **Paketmanager:** Homebrew
- **Version:** 0.7.10
- **Quellzusammenfassung:** Schema inspector for Terraform/OpenTofu providers
- **Homepage:** <https://github.com/minamijoyo/tfschema>
- **Repository:** <https://github.com/minamijoyo/tfschema>
- **Zuletzt aktualisiert:** 2026-07-26T00:50:39+02:00
- **Generiert:** 2026-08-03T19:37:03+00:00

## Executables

- tfschema (Alias)

## Installationsverhalten

- Bottle: nicht verfügbar

## Version und Aktualität

- Seite generiert: 2026-08-03
- Manager-Version: 0.7.10
## Projektgeschichte und Nutzung

tfschema is a schema inspector for Terraform and OpenTofu providers. It uses provider binaries and the plugin protocol to list resource types, show resource schemas, generate shell autocomplete data, and open provider documentation.

### Projektgeschichte

The project predates OpenTofu support but now documents both Terraform v1.x and OpenTofu v1.6+ support. Its README emphasizes dynamic inspection of installed provider binaries rather than static registry scraping.

The README devotes substantial space to provider-binary discovery. tfschema searches the working directory, vendored plugin directories, modern and legacy `.terraform` plugin layouts, global plugin directories, and GOPATH, reflecting Terraform's changing provider installation layout across versions.

### Adoptionsgeschichte

tfschema has the broadest Homebrew usage in this batch, though still niche in absolute terms. Homebrew formula metadata lists stable version 0.7.10 and higher install counts than the other Terraform helper tools here, matching its usefulness for both module authors and provider investigators.

### Wie es verwendet wird

A typical workflow installs tfschema, initializes a Terraform project so provider binaries are present, and then runs commands such as `tfschema resource list aws` or `tfschema resource show aws_iam_user`. Users can set `TFSCHEMA_ROOT_DIR` to point discovery at a different Terraform working directory.

### Warum Paket-Nerds sich dafür interessieren

For package-manager users, tfschema is significant because it exposes provider schemas without requiring a full Terraform plan or hand-reading provider docs. It is especially useful when comparing provider versions, exploring unfamiliar resources, or scripting schema inspection from a locally installed CLI.

### Zeitleiste

- 2024: GitHub tags list v0.7.8 in January and v0.7.9 in August.
- 2026: GitHub tags and Homebrew formula metadata list v0.7.10 in May.
- 2026: Homebrew formula metadata lists stable version 0.7.10 with bottled builds.

### Related projects

- Terraform CLI
- OpenTofu
- Terraform provider plugin protocol
- Terraform Registry provider documentation

### Quellen

- <https://formulae.brew.sh/api/formula/tfschema.json>
- <https://github.com/minamijoyo/tfschema#readme>
- <https://github.com/minamijoyo/tfschema/tags>


## Sicherheitshinweise

narrow executable package without higher-risk signals.

- **Geiger-Risiko:** grün / niedrig
- narrow executable package without higher-risk signals


## Combined YAML source

View the package source record on GitHub. [combined/tfschema.yml](https://github.com/mxcl/pkgdb/blob/main/combined/tfschema.yml)


## Quellen

- pkg.so package database
- Geiger risk classifier
- curated package history
- pkgdb category and tag curation
- cross-ecosystem install command graph