Automic VaultAutomic Vault

brew

livekit-cli mit Homebrew, Nix, winget installieren

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

Installation

Weitere Installationsbefehle

macOS

Homebrewverifiziert · 100%
brew install livekit-cli

local Homebrew formula metadata

Linux

Nixverifiziert · 92%
nix profile install nixpkgs#livekit-cli

nixpkgs package indexes · pkgs/by-name/li/livekit-cli/package.nix · Quelle: api.github.com

Windows

Windows Package Managerverifiziert · 92%
winget install --id LiveKit.LiveKitCLI -e

Windows Package Manager source index · LiveKit.LiveKitCLI · Quelle: cdn.winget.microsoft.com

Überblick

Paketzusammenfassung

Command-line interface to LiveKit

Befehle und Aliase

  • livekit-cli
  • lk

Verlauf

Projektgeschichte und Nutzung

LiveKit CLI is the terminal interface for LiveKit projects. It packages common developer and operator workflows around LiveKit Cloud, self-hosted LiveKit servers, access tokens, rooms, egress, load testing, app templates, and agents.

Projektgeschichte

The livekit/livekit-cli repository was created on May 10, 2021, shortly before LiveKit's public launch in July 2021. The CLI grew alongside LiveKit's open source SFU and SDK ecosystem as the project moved from realtime audio/video infrastructure toward a broader agent and voice-AI platform.

LiveKit documentation describes the CLI, invoked as lk, as the primary interface for managing LiveKit Cloud projects, creating applications from templates, and deploying agents. The GitHub README also documents older core workflows such as token generation, room APIs, egress management, participant simulation, and load testing.

Adoptionsgeschichte

The CLI's adoption follows LiveKit's developer adoption rather than a separate ecosystem. As LiveKit became a self-hostable and managed realtime stack, the CLI became the practical bridge between package-manager installation and day-to-day project setup.

By June 2024, LiveKit said its platform was used by more than 20,000 developers; the CLI sits in that workflow as a setup and management tool for both cloud projects and local/self-hosted testing.

Wie es verwendet wird

Developers install LiveKit CLI with Homebrew, a shell installer, winget, or source builds. The documented precedence order for command parameters is command-line flags, environment variables, local configuration files such as ./livekit.toml, and then default project configuration.

The CLI can create access tokens, call LiveKit APIs, join rooms as a participant, publish demo media, start and manage egresses, run load tests, create app templates, authenticate to LiveKit Cloud, and deploy agents.

Warum Paket-Nerds sich dafür interessieren

livekit-cli is a good example of a modern infrastructure CLI that is both a package-manager binary and a cloud control surface. Its aliases and package names matter because users may invoke either livekit-cli or lk depending on installation path and documentation vintage.

For package maintainers, it combines typical Go CLI distribution with multimedia build considerations: the README notes audio and console subsystem dependencies around CGO, PortAudio, and WebRTC audio processing for source builds.

Zeitleiste

  • 2021-05-10: The livekit/livekit-cli repository was created.
  • 2021-07-07: LiveKit was publicly introduced as open source realtime audio/video infrastructure.
  • 2024-06-04: LiveKit reported more than 20,000 developers using the platform.
  • 2026-06-30: The livekit/livekit-cli repository showed active updates through GitHub metadata.

Related projects

  • The CLI is related to the LiveKit server, LiveKit Cloud, LiveKit Agents, client SDKs, server SDKs, egress, ingress, SIP, and LiveKit app template repositories.

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.
  • Installiert mit 1 Laufzeitabhängigkeiten.
  • Build-Metadaten listen 2 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
./livekit.toml

Credential files

Credential-bearing paths to review before unattended agent runs.

Unix
./livekit.toml

Executables

Installierte Executables

BefehlArtSichtbarkeitHinweis
livekit-clicliglobales Executable
lkcliglobales 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-Version2.18.2
Manager aktualisiert2026-07-25
lokale DatenOK
Upstreamaktuell
neueste erkannte Versionv2.18.2

https://github.com/livekit/livekit-cli

  • OKEs wurden keine Aktualitätswarnungen generiert.

Installationsmetadaten

Paketmetadaten

Paketschlüsselbrew:livekit-cli
Version2.18.2
PaketmanagerHomebrew
Paketmanager-Seitehttps://formulae.brew.sh/formula/livekit-cli
Homepagehttps://livekit.io
Repositoryhttps://github.com/livekit/livekit-cli
Upstream-Dokumentationhttps://docs.livekit.io/reference/developer-tools/livekit-cli
LizenzApache-2.0
Quellarchivhttps://github.com/livekit/livekit-cli/archive/refs/tags/v2.18.2.tar.gz
Zuletzt aktualisiert2026-07-25T00:14:25Z
Pulseupdated
Abhängigkeitenportaudio
Build-Abhängigkeitengo, pkgconf
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 Namelivekit-cli
Version Scheme0
Revision0
Head VersionHEAD
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%

livekit-cli

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

LiveKit.LiveKitCLI

winget install --id LiveKit.LiveKitCLI -e
  • normalized package name match
  • Abgeglichen nach: Livekit Cli
Windows Package Manager source index · cdn.winget.microsoft.com · Windows Package Manager source index: LiveKit.LiveKitCLI 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