Snyk CLI exit codes: 0, 1, 2 for results and 3, 69, 75, 77 for environment errors

TL;DR

Per Snyk docs: exit 1 means "issues found", not "broken" - only exit 2 and above indicate execution problems. 0 means the command ran and found no issues.

Steps

1. Per Snyk docs: exit 1 means "issues found", not "broken" - only exit 2 and above indicate execution problems.
2. 0 means the command ran and found no issues.

When to use

You are seeing this: Per Snyk docs: exit 1 means "issues found", not "broken" - only exit 2 and above indicate execution problems. Use this skill when you run into "Snyk CLI exit codes: 0, 1, 2 for results and 3, 69, 75, 77 for environment errors".

When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

Versions

No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.

Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.

Source: Problem: Interpreting the snyk CLI exit code in CI. 0 means the command ran and found no issues. 1 means it ran and found issues - not a failure. 2 means the command did not execute successfully (review debug output and error codes). Error-catalog codes add: 3 no supported files or projects detected, 69 service unavailable, 75 temporary failure or maintenance window, 77 no permission.

Verified resolution: Per Snyk docs: exit 1 means "issues found", not "broken" - only exit 2 and above indicate execution problems.

Source URL: https://github.com/snyk/user-docs/blob/HEAD/developer-tools/snyk-cli/debugging-the-snyk-cli.md