# bltool mit Homebrew installieren

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

## Installation

```sh
sudo av install brew:bltool
```

Weitere Installationsbefehle:

### macOS

- Homebrew (100%):

```sh
brew install bltool
```

  Evidenz: local Homebrew formula metadata

## Paketfakten

- **Paketschlüssel:** brew:bltool
- **Paketmanager:** Homebrew
- **Version:** 0.2.4
- **Quellzusammenfassung:** Tool for command-line interaction with backloggery.com
- **Homepage:** <https://github.com/ToxicFrog/bltool>
- **Repository:** <https://github.com/ToxicFrog/bltool>
- **Zuletzt aktualisiert:** 2026-07-17T17:53:01+09:00
- **Generiert:** 2026-08-03T19:37:03+00:00

## Executables

- bltool (Alias)

## Installationsverhalten

- Bottle: nicht verfügbar

## Version und Aktualität

- Seite generiert: 2026-08-03
- Manager-Version: 0.2.4
## Projektgeschichte und Nutzung

bltool is a Clojure command-line utility for moving game-library data into and out of Backloggery, with import paths for Steam and Xbox Live. The project README now marks it unmaintained and warns that it has issues with the current Backloggery site.

### Projektgeschichte

Ben "ToxicFrog" Kelly released bltool in 2013 as a command-line helper for managing a Backloggery game collection. Its release tags run from v0.1.0 in 2013 through v0.2.4 in 2017, and the README records an explicit unmaintained status update.

The tool was built with Leiningen and distributed as a Java jar/release zip, with Homebrew offered as the macOS package-manager path.

### Adoptionsgeschichte

bltool served a niche automation audience: Backloggery users who wanted bulk add, delete, filter, and import workflows rather than editing a game list by hand. The Homebrew formula made that niche tool easy to install on macOS.

### Wie es verwendet wird

The command reads from formats such as Backloggery, Steam, Xbox Live, text, EDN, and JSON, then writes to Backloggery operations or local files. Backloggery writes use command-line username and password options rather than a documented credentials file.

Examples in the README show Steam-to-text-to-Backloggery imports, duplicate filtering, and deletion workflows composed with ordinary shell commands.

### Warum Paket-Nerds sich dafür interessieren

bltool is interesting mostly as a frozen snapshot of personal-data plumbing around 2010s game-tracking sites: a Clojure jar packaged for Homebrew, shell pipelines, EDN/JSON interchange, and fragile integrations with consumer web services.

### Zeitleiste

- 2013: v0.1.0 tag published and README copyright names Ben "ToxicFrog" Kelly and Google Inc.
- 2014: v0.1.x releases continued with import and format workflows documented in the README.
- 2017: v0.2.4 tag published.
- 2021: README updated to say the project is no longer maintained.

### Related projects

- Backloggery is the primary destination service.
- Steam Community and Xbox Live are optional import sources.
- Leiningen is the documented build tool for source builds.

### Quellen

- <https://github.com/ToxicFrog/bltool#readme>
- <https://github.com/ToxicFrog/bltool/releases>
- source_facts.package-manager


## Sicherheitshinweise

narrow executable package without higher-risk signals.

- **Geiger-Risiko:** grün / niedrig
- narrow executable package without higher-risk signals


## Combined YAML source

View the package source record on GitHub. [combined/bltool.yml](https://github.com/mxcl/pkgdb/blob/main/combined/bltool.yml)


## Quellen

- pkg.so package database
- Geiger risk classifier
- curated package history
- pkgdb category and tag curation
- cross-ecosystem install command graph