projectdiscovery
[FEATURE] Rolling template release update support
Describe your feature request
As of now, nuclei templates merged into the main branch are not immediately available to users. User templates are updated only during project releases (typically every 2 weeks). If a new CVE is merged into the template project, users can't use it out of the box and must either manually clone the nuclei-templates each time or set up external automation.
but since we have real-time nuclei template feed API available in PDCP , it's now possible to serve these templates to users as soon as they are merged into the project.
It can be optional feature that will work when PDCP_API_KEY env or auth is configured and can be disabled when -duc or below env is configured like other template download options.
# Disable early template download from nuclei-templates project
export DISABLE_EARLY_TEMPLATES_PUBLIC_DOWNLOAD=true
Describe the use case of the feature
For cases like this — https://github.com/orgs/projectdiscovery/discussions/4764 — having the ability to run the latest templates without waiting for the 2-week release or manually cloning the template project (which requires additional template management) would be useful.
Describe alternatives you've considered
No response
Additional context
No response
I think it would be better if the design of the -update-templates option allowed users to choose between updating strategies either to the stable version (as the default) or to the latest version (from the HEAD of nuclei-templates repo) - like this composite action. This approach gives users more control & flexibility directly, instead of managing these updates through env. It feels more straightforward and user-friendly.
