Sandeep Singh

Option to list all JSON output keys name

1

### Please describe your feature request: A new option to list all the json output field keys name which can be further used with matchers / filters. ```yaml -ldv, -list-dsl-variables...

### Please describe your feature request: Like https://github.com/projectdiscovery/nuclei/issues/2368, using [tlsx](https://github.com/projectdiscovery/tlsx) for tls connection and tls data collection. Related / Impacted feature: - `-tls-grab` (flag) - `-tls-probe` (flag) - `tls-grab` (json...

### Please describe your feature request: When `-irr` option is used with JSON output, the response header fields contain values for the response header that can be updated to make...

### Please describe your feature request: Similar to https://github.com/projectdiscovery/nuclei/issues/2358, dsl expression based matcher / filter condition can be supported on available [json keys named fields](https://github.com/projectdiscovery/httpx/issues/750). ```yaml -mdc, -match-condition string[] match...

### Please describe your feature request: To make json output easy to consume, json output fields that contains `-` (dash) can be replaced with `_` (underscore) Reference: - https://stackoverflow.com/questions/13869627/unable-to-access-json-property-with-dash old...

### Please describe your feature request: As a user, I create multiple custom templates on a personal public / private GitHub repository that I wish to run / update while...

Depends on https://github.com/projectdiscovery/nuclei/issues/2253 ### Please describe your feature request: As nuclei engine supports multiple protocols that may expect different inputs varies from - - `host` - `host:port` - `scheme://host:port` -...

Currently, if multiple protocol outputs from the same template return true, only one is displayed or ignored, this behaviour can be updated / fixed as running multipe protocol from same...

### Discussed in https://github.com/projectdiscovery/nuclei/discussions/2553 - [ ] Support for all the filtering options for workflows (currently, only `-s/seveirty` is supported) > **Note:** supports need to be implemented similarly like currently...

Depends on https://github.com/projectdiscovery/nuclei/issues/2533 **Details:** ```yaml # TBD ``` **Related discussion:** - https://github.com/projectdiscovery/nuclei/discussions/2016