pkg.soopen package index

brew / Rang 9561

gvp mit Homebrew installieren

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

Installation

Weitere Installationsbefehle

macOS

Homebrewverifiziert · 100%
brew install gvp

local Homebrew formula metadata

Überblick

Paketzusammenfassung

Go versioning packager

Befehle und Aliase

  • gvp

Verlauf

Projektgeschichte und Nutzung

gvp, the Go Versioning Packager, is a shell-oriented helper for isolating Go project dependencies by changing GOPATH, GOBIN, and PATH to use a project-local .godeps directory. It belongs to the pre-Go-modules era of Go dependency management, when GOPATH isolation and vendoring helpers were common.

Projektgeschichte

The GitHub repository was created on 2014-02-01, and the first GitHub release was published on 2014-02-04. The README says gvp was based on gst, a similar dependency-isolation tool for Ruby gems, and was designed as a companion to gpm while remaining usable on its own.

The release stream moved quickly in 2014 and 2015, with releases for environment handling, plugin support, and other fixes. GitHub releases list v0.3.0 on 2015-07-28 as a release named 'Major improvements and fixes'.

Adoptionsgeschichte

gvp was packaged for Homebrew and documented a Unix-style source installation flow. Its adoption was tied to Go developers who wanted project-local dependencies before Go modules made module-aware dependency resolution the normal path.

The README's examples combine gpm and gvp, showing a workflow where gpm handled dependency lists and gvp switched the shell into the right dependency context for a project. That made it useful to people juggling multiple GOPATH-based projects with conflicting dependency versions.

Wie es verwendet wird

gvp is sourced into the shell because a child process cannot modify the parent shell environment. Once sourced, gvp in adjusts GOPATH and GOBIN to the .godeps tree, gvp out restores the prompt and environment, gvp version prints version information, and unknown subcommands can be delegated to executables named gvp-<command> through the plugin mechanism.

The README also documents autoenv integration: a project can place a source command in .env so entering the directory activates the gvp environment automatically.

Warum Paket-Nerds sich dafür interessieren

gvp is historically interesting because it packages the GOPATH workaround era into a tiny tool. It shows how Go users handled isolation before module files became the standard metadata, and it connects Go packaging practice to earlier language-specific environment switchers such as Ruby's gst.

Zeitleiste

  • 2014-02-01: Public GitHub repository created.
  • 2014-02-04: First GitHub release, v0.01, published.
  • 2014-09-28: v0.2.0 release published.
  • 2015-07-28: v0.3.0 release published with major improvements and fixes.
  • 2015-10-07: Repository metadata records later activity in the project.

Related projects

  • gpm: README describes gvp as a companion tool for Go dependency management.
  • gst: README says gvp was based on this Ruby-gem dependency-isolation tool.
  • autoenv: README documents automatic activation through .env files.
  • Go GOPATH tooling: gvp's purpose is to isolate GOPATH-era project dependencies.

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

  • Es wurden keine Homebrew-Bottle-Metadaten erfasst.

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.

Executables

Installierte Executables

BefehlArtSichtbarkeitHinweis
gvpExecutableindexiertes ExecutableAus dem lokalen Executable-Index erkannt.

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-08-03
Manager-Version0.3.0
Manager aktualisiert2026-08-02
lokale Datenunbekannt
Upstreamnicht verfügbar
neueste erkannte Versionnicht erkannt
  • OKEs wurden keine Aktualitätswarnungen generiert.

Installationsmetadaten

Paketmetadaten

Paketschlüsselbrew:gvp
Version0.3.0
PaketmanagerHomebrew
Homepagehttps://github.com/pote/gvp
Repositoryhttps://github.com/pote/gvp
Zuletzt aktualisiert2026-08-02T20:52:09+09:00
Pulseupdated
Bottlenicht erfasst
Dienstkeiner deklariert

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
  • cross-ecosystem install command graph
  • curated package history
  • pkg.so package database
  • pkgdb category and tag curation