Automic VaultAutomic Vault

brew

svu mit Homebrew, MacPorts, Nix installieren

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

Installation

Weitere Installationsbefehle

macOS

Homebrewverifiziert · 100%
brew install svu

local Homebrew formula metadata

MacPortsverifiziert · 94%
sudo port install svu

MacPorts ports tree · devel/svu/Portfile · Quelle: api.github.com

Linux

Nixverifiziert · 92%
nix profile install nixpkgs#svu

nixpkgs package indexes · pkgs/by-name/sv/svu/package.nix · Quelle: api.github.com

Überblick

Paketzusammenfassung

Semantic version utility

Befehle und Aliase

  • svu

Verlauf

Projektgeschichte und Nutzung

svu is a small command-line utility for deriving semantic versions from Git history. It is aimed at release scripts and CI workflows that want version bumps to follow SemVer and Conventional Commits without carrying a larger release-management system.

Projektgeschichte

The caarlos0/svu repository was created on GitHub in December 2017 and describes the tool as a semantic version utility. Its README presents the project as a helper for release scripts and workflows, with commands that increment version components or calculate the next version from commit history.

Adoptionsgeschichte

The README documents installation through Homebrew, apt/yum repositories, Docker images, go install, and GitHub releases. The input package facts also list Homebrew, MacPorts, and Nix packaging, which is typical for a small Go CLI that package-manager users install directly into release pipelines.

Wie es verwendet wird

The central command is `svu next`, which inspects `git log` and maps commit-message patterns such as fixes, features, and breaking changes to patch, minor, or major version bumps. The README also documents a repository-local `.svu.yml` file for setting flag defaults.

Warum Paket-Nerds sich dafür interessieren

svu matters to package and release-tool users because it reduces semantic-version calculation to a composable Unix-style executable. It fits especially well in formula update scripts, CI jobs, and Git tag automation where maintainers want predictable version output rather than a full changelog or release platform.

Zeitleiste

  • 2017: GitHub repository created and v0.0.1 released.
  • 2020: v1.0.0 released.
  • 2026: v3.4.1 listed as the latest GitHub release during research.

Related projects

  • svu explicitly points users to the SemVer specification and advertises Conventional Commits compatibility through its README badges and bump rules.

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

Executables

Installierte Executables

BefehlArtSichtbarkeitHinweis
svucliglobales 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-08
Manager-Version3.4.1
Manager aktualisiert2026-05-01
lokale DatenOK
Upstreamaktuell
neueste erkannte Versionv3.4.1

https://github.com/caarlos0/svu

  • OKEs wurden keine Aktualitätswarnungen generiert.

Installationsmetadaten

Paketmetadaten

Paketschlüsselbrew:svu
Version3.4.1
PaketmanagerHomebrew
Paketmanager-Seitehttps://formulae.brew.sh/formula/svu
Homepagehttps://github.com/caarlos0/svu
Repositoryhttps://github.com/caarlos0/svu
Upstream-Dokumentationhttps://github.com/caarlos0/svu#readme
LizenzMIT
Quellarchivhttps://github.com/caarlos0/svu/archive/refs/tags/v3.4.1.tar.gz
Zuletzt aktualisiert2026-05-01T18:22:26Z
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 Namesvu
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%

svu

nix profile install nixpkgs#svu
  • normalized package name match
  • Abgeglichen nach: Svu
nixpkgs package indexes · api.github.com · nixpkgs package indexes: pkgs/by-name/sv/svu/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1
MacPorts95%

svu

sudo port install svu
  • normalized package name match
  • Abgeglichen nach: Svu
MacPorts ports tree · api.github.com · MacPorts ports tree: devel/svu/Portfile from https://api.github.com/repos/macports/macports-ports/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