bdo-cli 0.48.3 → 0.49.1

package/CHANGELOG.md

@@ -5,6 +5,55 @@ 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.49.1] (2026-10-29)
+
+### Security
+
+- **Redaction: values starting with `-` and multi-part shell words.** A secret
+  beginning with `-` was left in plain text for env assignments
+  (`DATABASE_PASSWORD=-…`), `curl -u alice:-…`, mysql `-p-…` and
+  `password=-…` — only a value after a `--flag` may be the next flag. And a
+  value the shell reads as one word but built from several quoted and
+  unquoted parts was masked only in part (`--password "abc"defgh` kept
+  `defgh`) or not at all (`abc"d e"f`). The whole word is now masked; a value
+  that is exactly one quoted string still keeps its quotes, so JSON stays
+  valid, and `""`, `''` and `$VAR` / `"$VAR"` references are left alone.
+- **Redaction: `curl -u` arguments are one shell word too.** A credential
+  quoted as a whole and continued after the quote — `curl -u 'alice:abc'defgh`
+  — kept `defgh`, because the quoted-argument rule stopped at the closing
+  quote. The `-u` / `--user` / `-uUSER` / `--user=` argument is now captured
+  as one shell word and split at its first `:`: the user is kept and the rest
+  of the word masked, with quotes re-balanced. No `:` (curl prompts) and
+  `$VAR` references the shell expands (unquoted or in `"…"`) are left alone,
+  while a `$` inside `'…'` is literal and masked
+  (`curl -u 'alice:$literalSecret9'`). `--user` must be followed by `=` or a
+  space, so `--user-agent=client:1.0` is not touched.
+
+## [0.49.0] (2026-10-29)
+
+### Security
+
+- **Secret redaction covers far more forms.** What bdo stores locally
+  (tracking DB, tee recovery files, hook audit fields) is now masked for:
+  environment-style assignments whose name ends in a secret word
+  (`GITHUB_TOKEN=…`, `OPENAI_API_KEY=…`, `AWS_SECRET_ACCESS_KEY=…`) — the old
+  rule missed these because `_TOKEN` has no word boundary; passwords in URL
+  userinfo (`https://user:PASS@host`, `postgres://…`); secret-named flags with a
+  separate value (`--password X`, `--token X`); mysql `-pPASS` and
+  `curl -u user:PASS`; Cookie headers; Slack/Discord webhook URLs; AWS/Azure
+  signed-URL parameters; and Hugging Face, Docker Hub, DigitalOcean, PyPI,
+  SendGrid, Google OAuth and further GitLab token formats. A probe of 23
+  common forms went from 2 masked to all 23. Look-alikes are pinned as
+  untouched: `MAX_TOKENS=4096`, `GITHUB_TOKEN=$GH_TOKEN`, `--password-stdin`,
+  `--token-file`, `ssh://git@host:22`, `cargo test -p`, `docker run -p`,
+  mysql's `-P3306`. Values may be quoted and contain spaces
+  (`PASSWORD="my secret pass"`, `--password ' leading'`, `-p'a b'`,
+  `curl -u 'alice:a b'`, `my\ pass`): the whole value is masked and its quotes
+  kept, and a Cookie value containing quotes (`session="…"`) is masked whole.
+  Each rule now compiles only when its trigger substrings appear, so the
+  per-command cost dropped despite the larger rule set (e.g. ~0.2 ms for an
+  env token, ~0.005 ms for a command with no secret word, vs ~2.8 ms before).
+
 ## [0.48.3] (2026-10-27)
 
 ### Security

package/README.md

@@ -119,7 +119,7 @@ gh attestation verify "$(brew --cache bushido)" --repo tedorigawa001/TokenReduct
 ### Verify Installation
 
 ```bash
-bdo --version   # Should show "bdo 0.48.3"
+bdo --version   # Should show "bdo 0.49.1"
 bdo gain        # Should show token savings stats
 ```
 

package/package.json

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