Automic VaultAutomic Vault

brew

vespa-cli mit Homebrew, Nix installieren

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

Installation

Weitere Installationsbefehle

macOS

Homebrewverifiziert · 100%
brew install vespa-cli

local Homebrew formula metadata

Linux

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

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

Überblick

Paketzusammenfassung

Command-line tool for Vespa.ai

Befehle und Aliase

  • vespa
  • vespa-wrapper

Verlauf

Projektgeschichte und Nutzung

Vespa CLI is the official command-line client for Vespa, the open-source AI search and big-data serving platform. The CLI packages common Vespa developer and operator actions into a single Go-built binary: deploying applications, feeding and querying documents, sending authenticated requests, and automating Vespa Cloud operations.

Projektgeschichte

Vespa itself was open-sourced by Yahoo/Oath on September 27, 2017 as a big-data processing and serving engine for real-time search, recommendation, and personalization workloads. The open-source announcement positioned Vespa as the serving complement to batch and stream processing stacks such as Hadoop and Storm.

Vespa CLI was introduced on September 23, 2021. The announcement says Vespa users had historically deployed and interacted with applications through APIs or a Maven plugin, both of which had friction: API use meant copying dense terminal commands and Maven assumed a Java toolchain. The CLI was built as an official zero-dependency command-line tool for both self-hosted Vespa and Vespa Cloud.

In October 2023, Vespa.ai spun out of Yahoo as a separate company. Vespa's own announcement tied the spinout to the platform's evolution from Yahoo search, recommendation, and ad-serving infrastructure into a serving-time AI platform used for large datasets, vector search, and production relevance systems.

Adoptionsgeschichte

The CLI's adoption follows Vespa's adoption path: it became the normal local and cloud workflow surface for developers working with Vespa applications. Official documentation presents it as the command-line client for Linux, macOS, and Windows, and the command tree covers the everyday lifecycle from clone and deploy through feed, query, inspect, status, logs, tests, and production deployment.

Vespa's 2023 spinout announcement gives broader adoption context: Yahoo remained a major customer, the platform was serving personalized content and search use cases, and Vespa Cloud was already supporting production workloads. In that setting, the CLI is not just a convenience wrapper; it is the developer-facing entry point for a large hosted and self-managed search platform.

Wie es verwendet wird

Vespa CLI is used to clone sample applications, deploy application packages locally or remotely, deploy to Vespa Cloud, feed documents, query documents, and send authenticated custom requests. The docs also show it managing mTLS-related local state under `.vespa` and switching between local and cloud targets.

In package terms, `vespa` is the handle that turns Vespa from a server platform into an iterative developer workflow. A user can create or fetch an application package, deploy it, stream documents into it, run queries, inspect status, follow logs, and automate deployment operations without manually stitching together HTTP requests and authentication material.

Warum Paket-Nerds sich dafür interessieren

Vespa CLI is significant because it condenses a complex distributed search platform into a reproducible command-line workflow. For packagers and operators, it is the small binary that makes Vespa approachable on a laptop, in CI, and in cloud automation, while still mapping directly to production Vespa concepts such as tenants, applications, instances, zones, deployments, documents, and queries.

Zeitleiste

  • 2016-06-03: Vespa GitHub repository created.
  • 2017-09-27: Yahoo/Oath announced Vespa as open source on GitHub.
  • 2021-09-23: Vespa CLI introduced as the official zero-dependency command-line tool.
  • 2023-10-03: Vespa.ai announced it was spinning out of Yahoo as a separate company.

Related projects

  • Vespa: the search, recommendation, and AI serving platform controlled by the CLI.
  • Vespa Cloud: the hosted service targeted by the CLI for cloud deployment and operations.
  • Maven plugin and direct Vespa APIs: the older interaction methods the CLI was designed to simplify.

Sicherheitslage

Noch keine Protected-Tool-Abdeckung gefunden

Für vespa-cli wurde kein passendes lokales Secret-Handling-Manifest gefunden. Nucleus-Paketmetadaten bleiben hier veröffentlicht, damit künftige Abdeckung eine stabile Paket-URL hat.

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
~/.vespa./.vespa

Credential files

Credential-bearing paths to review before unattended agent runs.

Unix
~/.vespa/<tenant>.<application>.<instance>/data-plane-private-key.pem./.vespa/<tenant>.<application>.<instance>/data-plane-private-key.pem

Executables

Installierte Executables

BefehlArtSichtbarkeitHinweis
vespacliglobales Executable
vespa-wrappercliglobales 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-Version8.719.5
Manager aktualisiert2026-07-07
lokale DatenOK
Upstreamaktuell
neueste erkannte Versionv8.719.5

https://github.com/vespa-engine/vespa

  • OKEs wurden keine Aktualitätswarnungen generiert.

Installationsmetadaten

Paketmetadaten

Paketschlüsselbrew:vespa-cli
Version8.719.5
PaketmanagerHomebrew
Paketmanager-Seitehttps://formulae.brew.sh/formula/vespa-cli
Homepagehttps://vespa.ai
Repositoryhttps://github.com/vespa-engine/vespa
Upstream-Dokumentationhttps://docs.vespa.ai/en/clients/vespa-cli.html
LizenzApache-2.0
Quellarchivhttps://github.com/vespa-engine/vespa/archive/refs/tags/v8.719.5.tar.gz
Zuletzt aktualisiert2026-07-07T04:09:50Z
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 Namevespa-cli
Version Scheme0
Revision0
Bottle Stable Root URLhttps://ghcr.io/v2/homebrew/core
Deprecatedno
Disabledno
Keg Onlyno
URL Keys
  • stable

Source-Datenbank-Treffer

Andere Paketmanager-Einträge

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

Nix95%

vespa-cli

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

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