Skip to content

Exit Codes

Code Name Condition
0 Command completed The command produced its defined result. A review can contain failed package rows; inspect failed in JSON. Says nothing about what was found.
2 Error Analysis could not run or could not complete (network error, clone failure, unreadable config, invalid flag combination).
130 Interrupted Ctrl+C interrupted the operation. The CLI prints Interrupted. to stderr.

The exit code is not a verdict. A FLAGGED or INCONCLUSIVE package still exits 0, because the exit code answers "did the tool run", not "is this package safe". Findings are reported in the output and in --json. To gate a pipeline, read the JSON; see using TrustSight in CI.

This is a deliberate choice, and it is stated as an invariant in the security model: a verdict is evidence for a human decision, not an authority that halts a build on its own.

Per-command behaviour

trustsight review

  • 0: the review completed and results were printed. Individual package rows can be failed or incomplete; JSON consumers must inspect failed and coverage_gaps rather than infer a clean result from this status.
  • 2: a fatal error occurred before or during analysis (pacman -Qm failed, the AUR was unreachable, the config file is unreadable, the disk is full).
  • 130: Ctrl+C interrupted the command.

trustsight inspect

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

trustsight db check

Returns 0 only when SQLite reports ok. A corrupt database, including in --json mode, emits {"status": "corrupt", "errors": [...]} and exits 2.

trustsight history

Exit code 2 if the database cannot be opened, the package has never been analysed, or the limit is negative. An existing package with no retained rows returns 0 and an empty result.

trustsight lint-rules

Returns 0 when linting completes without errors, including when warnings or missing/superseded shipped-rule notices are reported. Returns 2 for lint errors or a nonexistent --file path.

trustsight full-aur

Exit code 2 on an incompatible flag combination (--watch with --export or --sign) or on a fatal pipeline error. Otherwise 0.

trustsight config

  • show: 0 on success, 2 on config read error.
  • set: 0 on success, 2 on write error.

Rationale

Exit 2 is reserved for operational failures where no useful result could be produced. Everything else is a result, and a result is data for the reviewer to act on. Encoding "flagged" in the exit status would make every score threshold a breaking change for anyone scripting the tool, and would invite the exact misreading the model rejects: treating a deterministic evidence sum as a pass/fail authority.