Sandeep Singh

### Please describe your feature request: ```yaml id: CVE-2022-4321 info: name: Test HTTP Template author: pdteam severity: info metadata: added_at: "2023-07-10" ```

```yaml -o, -output string output file to store proxify logs (default "proxify_logs.jsonl") -sr, -store-response store raw http request / response to output directory (default "proxify_logs") ``` ### Please describe your...

This includes - - Simplifying CLI options - Extending match / replace options - File input support (YAML rules) - Rules auto load support

As of now GCP provider fetches DNS name from GCP, it can be extended to fetch VM instances and other available public asset as well.

We can update the readme to include - - [x] Add docs + example - [x] Add integration test

### Please describe your feature request: goflags - https://github.com/projectdiscovery/goflags ### Describe the use case of this feature: to keep projects options uniform and easier to maintain.

Field option doesn't work with depth 1

1

### katana version: latest ### Current Behavior: Field option doesn't work with `-d 1` ```console echo https://www.mandiant.com/report-incident | katana -f email -d 1 -silent ``` ### Expected Behavior: Field option...

add option to load template profile.

1

```yaml -tp, -profile string template profile config file to run ``` EXAMPLE Runs: ```yaml nuclei -profile profiles/aws-cloud-config.yml # loads profile from installed template directory nuclei -profile aws-cloud-config # loads profile...

### Follow-up Ticket Idea - `context deadline exceeded` is too vague of error considering we have context propogated throughout nuclei and context with timeouts are used at various places. -...

follow up for - https://github.com/projectdiscovery/nuclei/pull/4941