Exit codes
b8e follows the grep/eslint convention: 0 clean, 1 findings, 2+ operational error — so a
CI step can swallow findings without swallowing a crash. Generated from the CLI_EXIT constant.
| Name | Code | Meaning |
|---|---|---|
clean | 0 | ran to completion, nothing gated. |
findings | 1 | ran, produced gating findings. ADVISORY: this is exactly the code a dogfood continue-on-error: true is meant to swallow. |
crash | 2 | the tool FAILED TO RUN to a valid result: an uncaught throw, an unresolvable --base, a broken baseline, or a failure to emit valid SARIF. DISTINCT from findings so a crash is never conflated with clean-or-advisory and never swallowed to green (#2785). |
auth | 2 | not authenticated / no usable credential (run b8e login). |
run | 3 | the audit ran but produced no usable result. |
config | 4 | missing/invalid invocation config: no org context, or an absent --project / --journeys / --group in a non-interactive run. |
environment | 5 | the browser/host environment isn’t ready for a launch. |