Automic VaultAutomic Vault

brew

Installer vespa-cli avec Homebrew, Nix

Consultez les chemins d'installation, exécutables, métadonnées et notes de sécurité de vespa-cli pour les workflows d'agents IA.

installation

Commandes d'installation supplémentaires

macOS

Homebrewvérifié · 100%
brew install vespa-cli

local Homebrew formula metadata

Linux

Nixvérifié · 92%
nix profile install nixpkgs#vespa-cli

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

aperçu

Résumé du paquet

Command-line tool for Vespa.ai

Commandes et alias

  • vespa
  • vespa-wrapper

historique

Historique du projet et usages

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.

Historique du projet

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.

Historique d'adoption

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.

Modes d'utilisation

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.

Pourquoi les passionnés de paquets s'y intéressent

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.

Chronologie

  • 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.

posture de sécurité

Aucune couverture d'outil protégé trouvée pour le moment

Aucun manifest local de gestion des secrets correspondant n'a été trouvé pour vespa-cli. Les métadonnées de paquet Nucleus restent publiées ici afin que la couverture future dispose d'une URL stable.

Comportement d'installation

  • Aucun hook post-install Homebrew n’est enregistré dans les métadonnées de formule.
  • Les métadonnées de bottle Homebrew sont disponibles pour 6 plateformes.
  • Les métadonnées de compilation listent 1 dépendances de compilation.

Revue recommandée

Avant une utilisation sans surveillance par un agent, vérifiez si l'outil lit des identifiants en clair, écrit un état distant, publie des artefacts ou lance des plugins.

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

exécutables

Exécutables installés

CommandeTypeExpositionNote
vespacliexécutable global
vespa-wrappercliexécutable global

fraîcheur

Version et fraîcheur

Ces signaux séparent l'âge de génération de la page, l'activité du gestionnaire de paquets et la comparaison avec les versions amont. Un retard de version n'est signalé que lorsqu'une URL de preuve et des versions comparables sont présentes.

page générée2026-07-26
version du gestionnaire8.719.5
gestionnaire mis à jour2026-07-07
données localesOK
amontà jour
dernière version détectéev8.719.5

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

  • OKAucun avertissement de fraîcheur n'a été généré.

métadonnées d'installation

Métadonnées du paquet

Clé du paquetbrew:vespa-cli
Version8.719.5
Gestionnaire de paquetsHomebrew
Page du gestionnaire de paquetshttps://formulae.brew.sh/formula/vespa-cli
Page d'accueilhttps://vespa.ai
Dépôthttps://github.com/vespa-engine/vespa
Docs amonthttps://docs.vespa.ai/en/clients/vespa-cli.html
LicenceApache-2.0
Archive sourcehttps://github.com/vespa-engine/vespa/archive/refs/tags/v8.719.5.tar.gz
Dernière mise à jour2026-07-07T04:09:50Z
Pulseupdated
Dépendances de compilationgo
Bouteilledisponible (sur arm64_linux, arm64_sequoia, arm64_sonoma, arm64_tahoe, sonoma, x86_64_linux)
post-install Homebrewnon défini
Serviceaucun déclaré

faits du registre

Détails de la base source

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

correspondances dans les bases sources

Autres enregistrements de gestionnaires de paquets

Les correspondances proviennent d’index externes de gestionnaires de paquets et restent séparées des liens de paquets Automic Vault locaux.

Nix95%

vespa-cli

nix profile install nixpkgs#vespa-cli
  • normalized package name match
  • Correspondance par : 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

piste source

Généré depuis les données du dépôt

Cette page est servie par av-web depuis l'artéfact SQLite privé des paquets généré par scripts/generate-pkg-sqlite.py.

Sources utilisées

  • 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