Skip to main content
Version: 1.4.4

Exit Codes

This document lists the custom exit codes used in the application and their meanings.

Exit CodeCommandReason for Exit
1mapInvalid AI option provided. The --ai option received a value that is not supported.
2runInvalid AI option provided. The --ai option received a value that is not supported.
3lazyloadInvalid URL or file path provided. The -u or --url option received a value that is not a valid URL or an existing file path.
4mapInvalid format provided. The --format option received a value that is not supported.
5mapMissing technology. The -t or --tech option was not specified.
6mapMissing directory. The -d or --directory option was not specified.
7refactorMapped JSON file does not exist. The -m or --mapped-json option received a value that is not an existing file path.
8refactorInvalid technology provided. The -t or --tech option received a value that is not supported.
9refactorOutput directory already exists. The -o or --output option received a value that is an existing directory path.
10runTechnology not detected. The tool was unable to detect the technology used by the target URL.
11runOutput directory already exists. The -o or --output option received a value that is an existing directory path.
12runInvalid URL provided. The -u or --url option received a value that is not a valid URL.
15stringsDirectory does not exist. The -d or --directory option received a value that is not an existing directory path.
16stringsMissing -e flag. The -p or --openapi flag was used without the -e flag.
17lazyloadSubsequent 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.
18runFirewall blocking API Gateway. The tool detected a firewall blocking the AWS API Gateway. Please try again without the API Gateway.
19mapAI 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.
20analyzeInvalid 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.
21lazyloadThe 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.
22lazyloadInvalid method name provided to --include-methods or --exclude-methods. The error output lists all valid method names.
23sourcemapsInput does not exist. The -i or --input option received a value that is not an existing file or directory path.
24sourcemapsOutput directory already exists. The -o or --output option received a value that is an existing directory path.
25refactorRemote dataset path not found. The --remote-collisions option received a path that does not exist in the HuggingFace dataset.
26refactorInvalid 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.
27proxyProxy not needed. --feasibility found no firewall/WAF blocking direct access to the target, so no proxy is required.
28proxyFirewall still blocking with proxy. --feasibility found the firewall/WAF still blocks the target even when routed through the configured proxy method.
29runProxy 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.
30lazyloadInvalid stagnation configuration. The --stagnation-timein value exceeds --lazyload-timeout, so stagnation monitoring could never trigger before the whole crawl times out.
31reportsj 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.