Automic VaultAutomic Vault

brew

boot-clj mit Homebrew, scoop, Nix, apt installieren

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

Installation

Weitere Installationsbefehle

macOS

Homebrewverifiziert · 100%
brew install boot-clj

local Homebrew formula metadata

Linux

Nixverifiziert · 92%
nix profile install nixpkgs#boot

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

Debian aptverifiziert · 92%
sudo apt install r-cran-boot

Debian stable package indexes · r-cran-boot · Quelle: deb.debian.org

Windows

Scoopverifiziert · 92%
scoop install extras/boot-clj

Scoop official bucket manifest trees · bucket/boot-clj.json · Quelle: api.github.com

Überblick

Paketzusammenfassung

Build tooling for Clojure

Verlauf

Projektgeschichte und Nutzung

Boot is a Clojure build framework and command-line script runner built around the idea that builds are programs. Its historical niche was giving Clojure projects programmable build pipelines, immutable filesets, classloader isolation, and ad-hoc scripting before the newer Clojure CLI tooling became common.

Projektgeschichte

Boot's own README describes it as both a Clojure build framework and an ad-hoc Clojure script evaluator. Instead of treating a build as a static project map, Boot evaluates Clojure scripts in a runtime environment that can add dependencies, compose tasks, and pass managed filesets between task middleware.

The public release line visible in the official GitHub releases starts with 2.0.0 prereleases in late 2014, moves through 2.0 release candidates in early 2015, and continues through the 2.7 and 2.8 series. The 2.8.3 release in April 2019 is the last stable release shown in the sampled GitHub release metadata.

Adoptionsgeschichte

Boot was adopted inside the Clojure community as an alternative to Leiningen-style project configuration, especially for workflows needing composable pipelines, ClojureScript builds, REPL-driven automation, and single-file scripts. The official README lists package-manager installation paths through Homebrew, Nix, AUR, Docker, Chocolatey, and Scoop, showing that it crossed from library ecosystem tooling into OS package collections.

Wie es verwendet wird

Users run `boot` with tasks such as `repl`, `pom`, `jar`, and `install`, or write a `build.boot` script that composes tasks in Clojure. The wrapper script or executable is a thin launcher that downloads and runs Boot's JARs from Maven, so `boot -u` historically handled updating the runtime bits.

Warum Paket-Nerds sich dafür interessieren

Boot is interesting to package nerds because it is both a package and a package bootstrapper: the installed command is a shim, while the real tool comes from Maven coordinates. It also illustrates a Clojure-era preference for programmable build logic, fileset immutability, and REPL-friendly build automation rather than declarative-only project files.

Zeitleiste

  • 2014: Boot 2.0.0 prereleases appear on GitHub.
  • 2015: Boot 2.0.0 release-candidate series continues.
  • 2016: Boot 2.6.0 and 2.7.x releases published.
  • 2018: Boot 2.8.0 and 2.8.x releases published.
  • 2019: Boot 2.8.3 published on GitHub.

Related projects

  • Related projects include Clojure itself, Maven repositories used for dependency resolution, Leiningen credentials compatibility noted in the curation data, boot-bin wrapper releases, and ClojureScript build workflows documented by the Boot project.

Sicherheitslage

Risikostufe: yellow

generalized runtime or code generation signal.

Risikoklassifikator

yellow Risiko · mittel Konfidenz · runtime

Warum

  • generalized runtime or code generation signal

Signale

  • text:build tool

Installationsverhalten

  • In den Formelmetadaten ist kein Homebrew-Post-install-Hook erfasst.
  • Homebrew-Bottle-Metadaten sind für 1 Plattformziele verfügbar.
  • Installiert mit 1 Laufzeitabhä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
$BOOT_HOME/boot.properties./boot.properties$BOOT_HOME/profile.boot./profile.boot./build.boot./.bootignore

Credential files

Credential-bearing paths to review before unattended agent runs.

Unix
$BOOT_HOME/credentials.gpg~/.lein/credentials.clj.gpg

Executables

Installierte Executables

BefehlArtSichtbarkeitHinweis
bootcliglobales 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.8.3
Manager aktualisiert2026-06-22
lokale DatenOK
Upstreamnot checked
neueste erkannte Versionnicht erkannt

https://github.com/boot-clj/boot

Installationsmetadaten

Paketmetadaten

Paketschlüsselbrew:boot-clj
Version2.8.3
PaketmanagerHomebrew
Paketmanager-Seitehttps://formulae.brew.sh/formula/boot-clj
Homepagehttps://boot-clj.github.io/
Repositoryhttps://github.com/boot-clj/boot
Upstream-Dokumentationhttps://github.com/boot-clj/boot#readme
LizenzEPL-1.0
Quellarchivhttps://github.com/boot-clj/boot/releases/download/2.8.3/boot.jar
Zuletzt aktualisiert2026-06-22T14:02:54-07:00
Pulseupdated
Abhängigkeitenopenjdk
Bottleverfügbar (auf all)
Homebrew post-installnicht definiert
Dienstkeiner deklariert

Registry-Fakten

Details aus der Quelldatenbank

Source DatabaseHomebrew formula API
Taphomebrew/core
Full Nameboot-clj
Version Scheme0
Revision2
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%

extras/boot-clj

scoop install extras/boot-clj
  • normalized package name match
  • Abgeglichen nach: Boot Clj
Scoop official bucket manifest trees · api.github.com · Scoop official bucket manifest trees: bucket/boot-clj.json from https://api.github.com/repos/ScoopInstaller/Extras/git/trees/master?recursive=1
Debian apt92%

r-cran-boot 1.3-31-1

GNU R package for bootstrapping functions from Davison and Hinkley

https://cran.r-project.org/package=boot

sudo apt install r-cran-boot
  • Section: gnu-r
  • Architecture: all
  • Source Package: boot
  • 1 Abhängigkeiten
  • installed executable or alias match
  • Abgeglichen nach: Boot
Debian stable package indexes · deb.debian.org · Debian stable package indexes: r-cran-boot from https://deb.debian.org/debian/dists/stable/main/binary-amd64/Packages.xz
Nix92%

boot

nix profile install nixpkgs#boot
  • installed executable or alias match
  • Abgeglichen nach: Boot
nixpkgs package indexes · api.github.com · nixpkgs package indexes: pkgs/by-name/bo/boot/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1
Ubuntu apt92%

r-cran-boot 1.3-30-1

GNU R package for bootstrapping functions from Davison and Hinkley

https://cran.r-project.org/package=boot

sudo apt install r-cran-boot
  • Section: universe/math
  • Architecture: all
  • Source Package: boot
  • 1 Abhängigkeiten
  • installed executable or alias match
  • Abgeglichen nach: Boot
Ubuntu 24.04 LTS package indexes · archive.ubuntu.com · Ubuntu 24.04 LTS package indexes: r-cran-boot from https://archive.ubuntu.com/ubuntu/dists/noble/universe/binary-amd64/Packages.gz

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