inkdex docs

Exit codes and environment

What inkdex and inkdex-vuln return, and the environment variables they read.

Exit codes

inkdex

CodeMeaning
0Success, results found.
1No results.
2Usage error, missing index, bad path, or no valid license.
3Internal error.

inkdex-vuln scan

CodeMeaning
0The scan ran (findings or not).
1--fail-on was given (or fail_on is set in .inkdex-vuln.toml) and a finding left after the filters and the ignores is at least that severe.
2The scan could not run: no index, bad path, no valid license.

inkdex diff --gate

1 when the head introduces a new unsanitized flow, 0 otherwise.

Environment variables

VariableWhat it does
INKDEX_TOKENA CI token: the license credential for pipelines.
INKDEX_KEYYour license key, instead of inkdex license activate.
INKDEX_HOMEWhere the license is kept (default ~/.config/inkdex).
NO_COLORPlain output: no colours, no progress display.
CISet by most CI systems: turns the progress display off.
RUST_LOGDebug logging on stderr (RUST_LOG=inkdex=debug), for support requests.

Global options

Every command accepts:

OptionWhat it does
-C DIRRun as if started in DIR.
--index PATHUse the .inkdex/ index at PATH.
--json / --jsonlOne JSON document / one JSON object per line.
-q, --quietPrint nothing; rely on the exit code.
--at REFRead a snapshot: worktree, a sha, HEAD~2, a tag.

On this page