@burtson-labs/bandit-stealth-cli 1.7.505 → 1.7.507

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (3) hide show
  1. package/README.md +1 -1
  2. package/dist/cli.js +1369 -1345
  3. package/package.json +1 -1
package/README.md CHANGED
@@ -511,7 +511,7 @@ bandit-agent --model qwen2.5-coder:32b
511
511
  bandit-agent --auto --output json "summarize results.csv" > summary.json
512
512
  ```
513
513
 
514
- Exit codes: `0` done, `1` failed (model, endpoint or runtime), `2` bad usage, `3` stopped before finishing (iteration limit, or no answer). With stdin as input there is nobody to answer an approval prompt, so approvals are denied; use `--auto`, or `BANDIT_PERMISSION_MODE=dangerous` inside a sandbox, for unattended runs.
514
+ Exit codes: `0` done, `1` failed (model, endpoint or runtime), `2` bad usage, `3` stopped before finishing (iteration limit, or no answer), `4` a call needed approval and nobody could give it. When stdin is not a terminal (a pipe, a redirected file, sbatch's `/dev/null`, a parent process's socket) there is nobody to answer an approval prompt: the call is not run, the model is told why, stderr names each call (`needs approval: run_command make install`), and `--output json` reports `"status": "needs_approval"` with an `approvalsNeeded` list. Use `--auto`, `BANDIT_PERMISSION_MODE=dangerous` inside a sandbox, or a `permissions.allow` rule in a trusted folder's `.bandit/settings.json`, for unattended runs.
515
515
 
516
516
  - **Sandboxed commands without Docker.** `bandit --sandbox` runs agent commands under Apptainer or SingularityCE when there is no Docker. See `bench/agent/CLUSTER.md`.
517
517