Exit Codes
This document lists the custom exit codes used in the application and their meanings.
| Exit Code | Command | Reason for Exit |
|---|---|---|
| 1 | map | Invalid AI option provided. The --ai option received a value that is not supported. |
| 2 | run | Invalid AI option provided. The --ai option received a value that is not supported. |
| 3 | lazyload | Invalid URL or file path provided. The -u or --url option received a value that is not a valid URL or an existing file path. |
| 4 | map | Invalid format provided. The --format option received a value that is not supported. |
| 5 | map | Missing technology. The -t or --tech option was not specified. |
| 6 | map | Missing directory. The -d or --directory option was not specified. |
| 7 | refactor | Mapped JSON file does not exist. The -m or --mapped-json option received a value that is not an existing file path. |
| 8 | refactor | Invalid technology provided. The -t or --tech option received a value that is not supported. |
| 9 | refactor | Output directory already exists. The -o or --output option received a value that is an existing directory path. |
| 10 | run | Technology not detected. The tool was unable to detect the technology used by the target URL. |
| 11 | run | Output directory already exists. The -o or --output option received a value that is an existing directory path. |
| 12 | run | Invalid URL provided. The -u or --url option received a value that is not a valid URL. |
| 15 | strings | Directory does not exist. The -d or --directory option received a value that is not an existing directory path. |
| 16 | strings | Missing -e flag. The -p or --openapi flag was used without the -e flag. |
| 17 | lazyload | Subsequent requests URLs file does not exist. This is an internal error, but can be caused if the strings module is not run with the -e flag first. |
| 18 | run | Firewall blocking API Gateway. The tool detected a firewall blocking the AWS API Gateway. Please try again without the API Gateway. |
| 19 | map | AI provider API key not found. Please provide it via --ai-api-key, or the OPENAI_API_KEY/ANTHROPIC_API_KEY environment variable matching --ai-provider. |
| 20 | analyze | Invalid rules found. Some of the rules provided are invalid, either failing schema validation or, when run with --determine-compatible-version, declaring a js_recon_version/js_recon_max_version that doesn't match what the rule's features actually require. |
| 21 | lazyload | The tool detected a header overflow. Please increase the limit by setting environment variable NODE_OPTIONS="--max-http-header-size=99999999". If the error still persists, please try again with a higher limit. |
| 22 | lazyload | Invalid method name provided to --include-methods or --exclude-methods. The error output lists all valid method names. |
| 23 | sourcemaps | Input does not exist. The -i or --input option received a value that is not an existing file or directory path. |
| 24 | sourcemaps | Output directory already exists. The -o or --output option received a value that is an existing directory path. |
| 25 | refactor | Remote dataset path not found. The --remote-collisions option received a path that does not exist in the HuggingFace dataset. |
| 26 | refactor | Invalid or unusable --detect-version-config value. The specified scat configuration has empty reliable_signatures.json for one or more known React versions, making it unsuitable for version detection. |
| 27 | proxy | Proxy not needed. --feasibility found no firewall/WAF blocking direct access to the target, so no proxy is required. |
| 28 | proxy | Firewall still blocking with proxy. --feasibility found the firewall/WAF still blocks the target even when routed through the configured proxy method. |
| 29 | run | Proxy WAF fallback failed. --proxy-waf-fallback determined the configured proxy couldn't bypass the firewall blocking the target (or the check itself failed). Single-URL mode only; batch mode skips the target instead. |
| 30 | lazyload | Invalid stagnation configuration. The --stagnation-timein value exceeds --lazyload-timeout, so stagnation monitoring could never trigger before the whole crawl times out. |
| 31 | report | sj binary not found. The --sj flag was set but the sj (swagger-jacker) binary is not present in PATH. Install it with go install github.com/BishopFox/sj@latest. |