mirror of https://github.com/projectdiscovery/nuclei.git synced 2025-12-24 06:05:28 +00:00

History

feat: issue tracker URLs in JSON + misc fixes (#4855 )

* feat: issue tracker URLs in JSON + misc fixes

* misc changes

* feat: status update support for issues

* feat: report metadata generation hook support

* feat: added CLI summary of tickets created

* misc changes

2024-03-10 22:02:42 +05:30

flow

memory leak fixes and optimizations (#4680 )

2024-01-31 01:59:49 +05:30

generic

fix concurrent map writes in tmplexec package (#4718 )

2024-02-02 21:36:48 +05:30

multiproto

introduce scan context (#4373 )

2023-11-28 00:24:45 +05:30

doc.go

nuclei v3 : misc updates (#4247 )

2023-10-17 17:44:13 +05:30

exec.go

feat: issue tracker URLs in JSON + misc fixes (#4855 )

2024-03-10 22:02:42 +05:30

interface.go

introduce scan context (#4373 )

2023-11-28 00:24:45 +05:30

README.md

nuclei v3 : misc updates (#4247 )

2023-10-17 17:44:13 +05:30

README.md

tmplexec

tmplexec also known as template executer executes template it is different from protocols package which only contains logic within the scope of one protocol. tmplexec is resposible for executing Template with defined logic. with introduction of multi protocol and flow templates (deprecated package protocols/common/executer) did not seem appropriate/helpful anymore as it is outside of protocol scope and deals with execution of template which can contain 1 requests , or multiple requests of same protocol or multiple requests of different protocols. tmplexec is responsible for executing template and handling all logic related to it.

Engine/Backends

Currently there are 3 engines for template execution

Generic => executes request[s] of same/one protocol
MultiProtocol => executes requests of multiple protocols with shared logic between protocol requests see multiprotocol
Flow => executes requests of one or multiple protocol requests as specified by template in javascript (aka flow) flow