# lando-cli mit Homebrew, winget installieren

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

## Installation

```sh
sudo av install brew:lando-cli
```

Weitere Installationsbefehle:

### macOS

- Homebrew (100%):

```sh
brew install lando-cli
```

  Evidenz: local Homebrew formula metadata

### Windows

- winget (92%):

```sh
winget install --id Lando.Lando -e
```

  Evidenz: Windows Package Manager source index: Lando.Lando from https://cdn.winget.microsoft.com/cache/source.msix

## Paketfakten

- **Paketschlüssel:** brew:lando-cli
- **Paketmanager:** Homebrew
- **Version:** 3.26.7
- **Quellzusammenfassung:** Cli part of Lando
- **Homepage:** <https://docs.lando.dev/cli>
- **Repository:** <https://github.com/lando/core>
- **Zuletzt aktualisiert:** 2026-07-03T06:58:38Z
- **Generiert:** 2026-08-03T19:37:03+00:00

## Executables

- lando (Alias)

## Installationsverhalten

- Bottle: nicht verfügbar

## Version und Aktualität

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

Lando CLI is the command-line surface for Lando, a Docker-based local development and DevOps tool that grew out of Kalabox. It packages local environment orchestration, recipes, services, proxying, events, and project-specific tooling behind a developer-friendly lando command.

### Projektgeschichte

In a 2017 Lando project post, Mike Pirog traced Lando back to Kalabox, which began as an internal Kalamuna tool for getting Pantheon sites running locally in about 10 to 15 minutes. Kalabox moved through a Vagrant/VirtualBox/Puppet-backed first version and a Docker-oriented Kalabox 2 before the maintainers decided the design was too monolithic and fragile.

The same post says Lando was born on 9 January 2017 after the Kalabox 2 experience, with goals of doing more with less code, using a single in-repository config file, opening the tool beyond Pantheon-specific Drupal and WordPress workflows, and making containerized project tooling feel more native.

### Adoptionsgeschichte

Lando's own 2017 adoption notes said it had diversified beyond Kalabox's Pantheon-heavy user base into Laravel, MEAN, Ruby, and other development use cases. The Lando docs later codified that model around a Landofile checked into a project repository, so a developer can clone a repo, run lando start, and get the local development stack in minutes.

### Wie es verwendet wird

The CLI has general Lando commands such as start, stop, rebuild, logs, info, ssh, config, update, and destroy; tooling commands defined by individual Landofiles; and management commands used by setup and plugin workflows. Project config centers on .lando.yml plus base and local override files, while global CLI config can live in ~/.lando/config.yml.

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

Lando CLI is package-relevant because it turns a local Docker Compose ecosystem into a reproducible per-project developer tool. The Homebrew formula is the ergonomic entry point for macOS and Unix developers who want lando on PATH without manually wiring the JavaScript runtime pieces.

### Zeitleiste

- 2016-09-19: Kalabox 2 was released.
- 2016-11-25: The last Kalabox release was cut before the pivot.
- 2017-01-09: Lando was born as the post-Kalabox redesign.
- 2017-10-24: The Lando project published its Kalabox-to-Lando history and early adoption notes.
- 2026-04-28: The lando/core repository listed v3.26.4 among its releases.

### Related projects

- Lando is related to Kalabox, Docker, Docker Compose, Pantheon local development, Platform.sh workflows, Drupal, WordPress, Laravel, MEAN, Ruby, and Lando's plugin and recipe ecosystem.

### Quellen

- <https://docs.lando.dev/cli>
- <https://docs.lando.dev/config/global.html>
- <https://docs.lando.dev/getting-started/what-it-do.html>
- <https://docs.lando.dev/landofile>
- <https://github.com/lando/core>
- <https://lando.dev/blog/2017/10/24/journey-lando.html>


## Sicherheitshinweise

narrow executable package without higher-risk signals.

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


## 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

- Unix: .lando.yml, .lando.base.yml, .lando.dist.yml, .lando.upstream.yml, .lando.local.yml, ~/.lando/config.yml
## Andere Paketmanager-Einträge

- winget - Lando.Lando: installed executable or alias match | Windows Package Manager source index: Lando.Lando from https://cdn.winget.microsoft.com/cache/source.msix


## Combined YAML source

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


## Quellen

- pkg.so package database
- Geiger risk classifier
- curated configuration and credential file locations
- curated package history
- pkgdb category and tag curation
- external package-manager database matches
- cross-ecosystem install command graph