Olivier Cervello

e.g: when feroxbuster is used with a large depth count or too many scans, it will enter a FUTEX_WAIT state waiting for user input and also hang on machine resources...

it's feasible to get live JSON lines output with `--silent --json` instead of tailing the JSON file

Make no color mode work for terminals that don't have color support

when `-proxy auto` is passed and no HTTP_PROXY defined, should fail gracefully with a warning.

# Explanation You can debug specific secator components by setting **debug components**: ```sh export SECATOR_DEBUG_COMPONENT="comp1,comp2,comp3" # OR secator config set debug.component comp1,comp2,comp3 ``` Note that activating a component will automatically...

It would be very beneficial to be able to chain workflows with the result of the previous workflows using the JSON report: ```sh secator w url_crawl http://testphp.vulnweb.com secator w url_vuln...

To replace `secator u install`, use `secator update` instead: - [ ] Run `secator health` - [ ] Update `secator` version - [ ] Update or install tools - [...

Some tools require their own configs. In `secator`'s `config.yaml` ```yaml ... tasks: dirsearch: config_path: /path/to/dirsearch/config.yaml # or config: | # inline YAML / .ini / .conf config_type: YAML ```