^{Originally posted by dogancanbakir September 10, 2025}
See the initial discussion: #4690

Notes from internal discussion @Mzack9999 and I:

During template updates, instead of rename, we create a new template, leaving outdated ones behind
The default nuclei-templates folder should be like a git repository, this way renames and deletions would be tracked correctly. Actually I guess we only unzip directly
Somehow we need to identify with template history, which ones are dupes based on content similarity and implement an auto-fix mechanism like to delete them if they were not altered and have only been renamed elsewhere, but I guess it's not super trivial and might take some time. We can mirror nuclei-templates since GH rate limit can cause issues.