Automic VaultAutomic Vault

brew

brename mit Homebrew, scoop installieren

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

Installation

Weitere Installationsbefehle

macOS

Homebrewverifiziert · 100%
brew install brename

local Homebrew formula metadata

Windows

Scoopverifiziert · 92%
scoop install main/brename

Scoop official bucket manifest trees · bucket/brename.json · Quelle: api.github.com

Überblick

Paketzusammenfassung

Cross-platform command-line tool for safe batch renaming via regular expressions

Befehle und Aliase

  • brename

Verlauf

Projektgeschichte und Nutzung

brename is a Go command-line batch-renaming tool focused on safe regular-expression based file and directory renames. Its distinguishing features are dry runs, conflict detection, cross-platform path safety, filters, recursive operation, and undo support.

Projektgeschichte

The GitHub repository was created in September 2013. The README presents brename as a practical cross-platform tool for safely batch renaming files and directories via regular expression.

The project evolved around safety checks that plain mv or rename commands do not provide, such as detecting existing targets, newly overwritten paths, empty target paths, and Windows-problematic path endings.

Adoptionsgeschichte

The official README lists prebuilt release binaries for Linux, macOS, and Windows, plus installation through Conda, Homebrew, Arch AUR, Scoop, and source builds. The input package facts also record Homebrew and Scoop packaging.

Its adoption is niche but practical: users who need repeatable bulk renames get a single static-style CLI rather than shelling together find, sed, mv, and platform-specific rename variants.

Wie es verwendet wird

The README documents pattern replacement with -p and -r, dry-run mode, include and exclude filters, recursive operation, directory renaming, key-value replacement files, ascending-number replacements, extension preservation, listing matches, and undoing the last successful operation.

Cross-platform safety is a major usage theme. The README calls out case-insensitive filesystems such as FAT and NTFS and documents flags for case-insensitive or case-sensitive path handling.

Warum Paket-Nerds sich dafür interessieren

brename is not a foundational package, but it is a useful example of a modern single-purpose Go CLI that packages well across Homebrew, Scoop, Conda, and downloadable release archives.

For package maintainers, it sits in the long family of rename tools while emphasizing safety and portability rather than just exposing a regular-expression substitution primitive.

Zeitleiste

  • 2013-09: The brename GitHub repository was created.
  • 2025: Official repository metadata showed activity into August 2025.
  • 2025: The README documented brename 2.14.0 release binaries for Linux, macOS, and Windows.

Related projects

  • Traditional Unix mv and rename commands are the simpler tools brename's safety checks are meant to improve upon.
  • Go is the implementation language and source-build toolchain named by the README.
  • Scoop and Homebrew are package-manager channels documented by the README and input facts.

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

Executables

Installierte Executables

BefehlArtSichtbarkeitHinweis
brenamecliglobales 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-25
Manager-Version2.14.0
Manager aktualisiert
lokale DatenOK
Upstreamaktuell
neueste erkannte Versionv2.14.0

https://github.com/shenwei356/brename

  • InfoNo package-manager update timestamp was available.niedrig Konfidenz

Installationsmetadaten

Paketmetadaten

Paketschlüsselbrew:brename
Version2.14.0
PaketmanagerHomebrew
Paketmanager-Seitehttps://formulae.brew.sh/formula/brename
Homepagehttps://github.com/shenwei356/brename
Repositoryhttps://github.com/shenwei356/brename
Upstream-Dokumentationhttps://github.com/shenwei356/brename#readme
LizenzMIT
Quellarchivhttps://github.com/shenwei356/brename/archive/refs/tags/v2.14.0.tar.gz
Build-Abhängigkeitengo
Bottleverfügbar (auf arm64_linux, arm64_sequoia, arm64_sonoma, arm64_tahoe, arm64_ventura, sonoma, ventura, x86_64_linux)
Homebrew post-installnicht definiert
Dienstkeiner deklariert

Registry-Fakten

Details aus der Quelldatenbank

Source DatabaseHomebrew formula API
Taphomebrew/core
Full Namebrename
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.

Scoop95%

main/brename

scoop install main/brename
  • normalized package name match
  • Abgeglichen nach: Brename
Scoop official bucket manifest trees · api.github.com · Scoop official bucket manifest trees: bucket/brename.json from https://api.github.com/repos/ScoopInstaller/Main/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 package history
  • external package-manager database matches
  • package relationship graph
  • package version freshness
  • package-page enrichment