Closes #4. Requested in Jan 2021 and attempted in PR #12, which could not be applied: its fork is gone and the code it patched has since been restructured. Its approach also overwrote ranges.txt in place, unvalidated, from a prompt that fired even in config-file mode where the written file is never read. --target accepts a comma-separated list of anything a target file line accepts (bare IP, CIDR, A-B range, address netmask) and takes precedence over both config.json's target_file and the interactive prompt, so it works in fully non-interactive runs. Three properties the earlier attempt lacked: - ranges.txt is never touched. It is the operator's engagement scope input, tracked in-repo as an empty template. Addresses go to cli_targets.txt in output_path via _atomic_write(), which also leaves a record of what each run actually targeted. - The value is validated before anything else happens, and a bad entry exits non-zero naming the token. Accepting a typo would produce a clean run over an empty target set — a false negative with a report attached. - Validation reuses the target-file parser. _parse_range_line() is extracted from _parse_target_ranges() so the CLI cannot accept syntax the scan then fails to read; the extraction is behaviour-preserving, including the silent skip of unparseable lines and the IPv6 file/line warning. _resolve_cli_target() holds the argv-to-tokens glue so the reject path is tested: main() is an interactive entry point excluded from coverage. 939 tests pass (32 new), 100% coverage. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

Commits

Commits on Aug 21, 2026

feat: add --target for scanning an address without a target file