CLI exit codes

The Veracode CLI returns an exit code to indicate whether your command succeeded or triggered an error. Some commands might have multiple exit codes.

The following table lists the exit codes and their meaning.

Exit code	Meaning
0	Command completed successfully.
1	Generic error.
2	Parser error. Check the command input and user permissions.
3	The veracode static scan or veracode scan command completed successfully, but the scanned application did not pass policy.
4	The command completed unsuccessfully. Either no artifacts were created by the autopackager during the veracode package command, or the packaging process encountered build warnings. The behavior depends on whether you used the --strict flag: - Without --strict: No artifacts were found. Common causes include missing source files or failed compilation. - With --strict: The packaging completed with build warnings that should be reviewed and addressed.
125	Out of memory.
126	Command failed. Check local system configuration.
127	Command not found. Check PATH configuration and command syntax.
128	Invalid argument. Retry the command.
130	Command terminated by user.