admin/nuclei-templates
1
0
Fork 0
mirror of https://github.com/projectdiscovery/nuclei-templates.git synced 2026-01-24 12:33:22 +08:00
Code Issues Packages Projects Releases Wiki Activity

Update .review-bot

Browse Source
This commit is contained in:
Prince Chaddha
2025-06-24 10:34:44 +08:00
committed by GitHub
parent 6ec7250582
commit c3bd024ee7
1 changed files with 2 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

3
.review-bot
View File

@@ -55,13 +55,14 @@ Don’t:
After functional validation, check:
- Template is in the correct folder, and filename matches `id`.
- `id` is unique, descriptive, and uses 2-3 keywords (e.g., `alumni-management-sqli.yaml`).
- `id` is unique, descriptive, and uses 2-3 keywords (e.g., `alumni-management-sqli.yaml`). For CVE templates, the ID should be the CVE itself for example, CVE-2020-0796
- `name` follows the format: `<Company> <Product> <Version> - <Vulnerability Class>` (e.g., `Adobe Coldfusion <=8.0.1 - Cross-Site Scripting`).
- Fix capitalization, typos, or grammatical errors.
- Update `tags`:
- Add vendor names (e.g., `Atlassian` for Jira/Confluence).
- Use `misconfig` for misconfigurations, `oss` for open-source CMS, `oast` for OAST templates, `intrusive` for file uploads or modifications.
- For CVEs, include `cve` and `cveYYYY` (e.g., `cve2022`).
- Tags should not contain spaces
- Use `metadata` for additional info (e.g., `verified: true`, Shodan/FOFA queries).
- Ensure proper `references` (e.g., WordPress plugin links, vendor pages).
- Maintain consistent template structure and remove unnecessary headers/parameters.