15.3. Exit Codes#

FlareInspect uses exit codes to communicate assessment results to CI/CD pipelines.

15.3.1. assess Exit Codes#

Condition

Exit Code

Assessment passes threshold and severity gate

0

Overall score < --threshold value

1

Any finding at or above --fail-on severity is FAIL

1

Assessment itself fails (invalid token, API error)

1

15.3.2. diff Exit Codes#

Condition

Exit Code

No regressions detected

0

One or more regressions detected

1

Error (invalid input, file not found)

1

15.3.3. Using Exit Codes in Shell#

flareinspect assess --token $TOKEN --ci --threshold 80
if [ $? -ne 0 ]; then
  echo "Security gate failed!"
  exit 1
fi

15.3.4. Using Exit Codes in CI#

Most CI systems automatically fail a step when a command exits with a non-zero code. No special handling is needed beyond running the command.