bdo-cli 0.48.0 → 0.48.2

package/CHANGELOG.md

@@ -5,6 +5,62 @@ All notable changes to Bushido (bdo) will be documented in this file.
 The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
 and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
+## [0.48.2] (2026-10-25)
+
+### Security
+
+- **`install.sh` verifies build provenance.** After the SHA-256 check, an
+  authenticated GitHub CLI runs `gh attestation verify`, pinned to this repo's
+  `release.yml` and the release tag; a mismatch aborts the install. The
+  checksum alone cannot catch a replaced release, since it ships in the same
+  release. Without an authenticated `gh` the installer warns and falls back to
+  the checksum; `BDO_VERIFY_ATTESTATION=require` refuses that, `=0` skips the
+  check. Releases before v0.47.1 have no attestations and are checksum-only.
+
+- **The Homebrew tap is checked daily against the release attestations.** The
+  formula pins each archive's sha256, so brew already rejects a replaced
+  release asset, but not a rewritten tap (e.g. a leaked tap token pointing url
+  and sha256 at another binary). A scheduled CI job now verifies that every
+  url in the live formula is this repository's release asset for the formula's
+  version, that its sha256 matches, that it carries build provenance from
+  `release.yml` at that tag, and that the formula tracks the latest release.
+  The README shows how to verify a Homebrew download yourself
+  (`gh attestation verify "$(brew --cache bushido)" …`).
+
+### Fixed
+
+- **`bdo --raw grep` without `grep` on PATH** (native Windows shells) still
+  capped, truncated and grouped the matches, because raw mode had no `grep` to
+  run and bdo's module ignored the switch. It now runs the same search through
+  ripgrep and prints every match in full as grep-style `file:line:content`,
+  with rg's exit code.
+- `install.sh` on x86_64 Linux downloaded `x86_64-unknown-linux-musl`, which
+  the release never publishes, so every such install failed. It now uses the
+  published `x86_64-unknown-linux-gnu` archive, and a test checks every target
+  the installer picks against the release's target list.
+
+## [0.48.1] (2026-10-21)
+
+### Security
+
+- **Hook permission gate: ANSI-C quoting and line-continued substitutions are
+  never auto-allowed.** `$'...'` quoting can hide real separators behind
+  escaped quotes (`git status $'a\'b'; other-cmd; echo $'c\'d'` looked like
+  one allowed `git status`), and a backslash-newline between `$`/`<`/`>` and
+  `(` (`$\⏎(…)`) slipped a command substitution past the gate, letting two
+  allowed commands combine (`git log $\⏎(echo --output=/path)` writes a file).
+  Both now defer to the agent's own permission prompt, across the Claude,
+  Cursor, Gemini and Copilot hooks.
+- **rustls-webpki 0.103.15 → 0.103.16 and webpki-roots 1.0.6 → 1.0.10**
+  (via `ureq`), fixing RUSTSEC-2026-0382 (certificate verification may accept
+  distrusted intermediates) and RUSTSEC-2026-0381 (bundled roots trust
+  distrusted emSign intermediates). Caught by the daily scheduled audit.
+- **`bdo curl` no longer buffers a whole response in memory.** Piped / redirected
+  output now goes straight from curl to the consumer (bytes arrive before the
+  transfer ends, exit status and failure bodies unchanged). On a terminal,
+  bdo captures at most 16 MiB to summarize; a larger response is streamed
+  byte-exact instead of growing memory without bound.
+
 ## [0.48.0] (2026-10-17)
 
 ### Features

package/README.md

@@ -76,6 +76,13 @@ curl -fsSL https://raw.githubusercontent.com/tedorigawa001/TokenReductionTool-BD
 > echo 'export PATH="$HOME/.local/bin:$PATH"' >> ~/.bashrc  # or ~/.zshrc
 > ```
 
+The installer always checks the archive's SHA-256. With an authenticated
+GitHub CLI (`gh auth login`) it also verifies the build provenance — that the
+archive was built by this repository's release workflow at that tag — and
+refuses to install if it doesn't match. Without `gh` it warns and relies on the
+checksum. `BDO_VERIFY_ATTESTATION=require` makes provenance mandatory;
+`BDO_VERIFY_ATTESTATION=0` skips it.
+
 ### Cargo
 
 ```bash
@@ -95,6 +102,14 @@ release):
 gh attestation verify bushido-aarch64-apple-darwin.tar.xz --repo tedorigawa001/TokenReductionTool-BDO
 ```
 
+Homebrew installs can be checked the same way, against the archive brew
+downloaded (CI also verifies the published formula against these attestations
+daily):
+
+```bash
+gh attestation verify "$(brew --cache bushido)" --repo tedorigawa001/TokenReductionTool-BDO
+```
+
 - macOS: `bushido-x86_64-apple-darwin.tar.xz` / `bushido-aarch64-apple-darwin.tar.xz`
 - Linux: `bushido-x86_64-unknown-linux-gnu.tar.xz` / `bushido-aarch64-unknown-linux-gnu.tar.xz`
 - Windows: `bushido-x86_64-pc-windows-msvc.zip`
@@ -104,7 +119,7 @@ gh attestation verify bushido-aarch64-apple-darwin.tar.xz --repo tedorigawa001/T
 ### Verify Installation
 
 ```bash
-bdo --version   # Should show "bdo 0.48.0"
+bdo --version   # Should show "bdo 0.48.2"
 bdo gain        # Should show token savings stats
 ```
 
@@ -436,7 +451,9 @@ BDO_RAW=1 bdo cargo test     # env var form, e.g. for a whole session
 ```
 
 - A command with a same-named program (`git`, `ls`, `cargo`, `grep`, …) runs
-  that program with your arguments unchanged.
+  that program with your arguments unchanged. Where there is no `grep` on PATH
+  (native Windows shells), `bdo --raw grep` runs the same search through
+  ripgrep and prints every match in full, as `file:line:content`.
 - `err` / `test` / `summary` run the command they wrap.
 - `read` shows the full file.
 - bdo-only commands (`gain`, `map`, …) have no unfiltered form and run as usual.

package/package.json

@@ -1,6 +1,6 @@
 {
   "artifactDownloadUrls": [
-    "https://github.com/tedorigawa001/TokenReductionTool-BDO/releases/download/v0.48.0"
+    "https://github.com/tedorigawa001/TokenReductionTool-BDO/releases/download/v0.48.2"
   ],
   "author": "Patrick Szymkowiak",
   "bin": {
@@ -91,7 +91,7 @@
       "zipExt": ".tar.xz"
     }
   },
-  "version": "0.48.0",
+  "version": "0.48.2",
   "volta": {
     "node": "18.14.1",
     "npm": "9.5.0"