Skip to content

Exit Codes

Code Name Condition
0 Success : CLEAN All reviewed packages scored ≤20. No FLAGGED or INCONCLUSIVE verdicts.
1 Flagged One or more packages scored >20 (FLAGGED) or produced an INCONCLUSIVE verdict.
2 Error Analysis failed for one or more packages (e.g. network error, repository clone failure, invalid configuration).

Per-command behaviour

trustsight review

Both exit code 1 and 2 are reachable:

  • 0: every analysed package has final_score ≤ 20. The summary table is printed and the tool exits cleanly.
  • 1: at least one package has final_score > 20 or the risk level is "Inconclusive". The summary table is printed, then exit 1.
  • 2: a fatal error occurred before or during analysis (e.g. pacman -Qm failed, AUR RPC unreachable, config file unreadable, disk full).

trustsight inspect

Exit code 2 if the analysis pipeline cannot complete (clone failure, database error). Otherwise exits 0; inspect is an information command and does not flag.

trustsight history

Exit code 2 if the database cannot be opened. Exits 0 even if no history is found for the requested package (an empty result is not an error).

trustsight config

  • show: exits 0 on success, 2 on config read error.
  • set: exits 0 on success, 1 if the key is not api_key or base_url, 2 on write error.

trustsight sandbox

Not yet implemented. Exits 2 with an error message.

Rationale

The exit code design follows the principle that CLEAN is the default expected state: 81.5 % of benign diffs score 0. Exit 1 is a deliberate signal that the review found something requiring human attention. Exit 2 is reserved for operational failures where no useful result could be produced.