loading
Loading content
loading
Utilities
Organize all the community Nuclei templates from across the ecosystem in one place.
overview
cent clones the scattered community nuclei template repositories and gathers their YAML checks into a single folder. The official ProjectDiscovery set is large, but plenty of useful detection lives in personal and team repos that nuclei does not pull by default, and cent collects that long tail.
A config file lists the repositories to clone. cent fetches them in parallel, keeps only the YAML templates unless you ask for full folders, and writes one ready-to-use directory you point nuclei at. Rerun it whenever you want the newest community detections.
On Trickest, cent is a Utilities node that takes a config and writes a folder of templates. Run it ahead of a nuclei stage to feed the scanner an expanded, community-sourced template set, then scope the scan itself by tags or severity.
source github.com/xm1k3/cent
use cases
Pull community templates from many repositories into one folder so a nuclei scan checks for far more than the default set ships with.
Maintain a config of trusted template repos and rerun cent to assemble a single, consistent directory the rest of your workflows share.
Run cent before each scan cycle so newly published community detections are pulled in and nuclei runs against current checks.
Let cent save only the template files by default, or keep full folders with --keepfolders when a repo's structure matters, so the output stays lean.
reference
| Name | Type | Flag | Description |
|---|---|---|---|
| config | FILE | · | Config file listing the template repositories to clone. |
| threads | STRING | --threads | Threads to use when cloning repositories (default 10). |
| keepfolders | BOOLEAN | --keepfolders | Keep full folders; by default cent saves only the YAML files. |
| console | BOOLEAN | --console | Print progress and collected templates to the console. |
Showing key inputs. cent exposes 4 inputs in total.
example
# collect the configured community template repos into one foldercent --config repos.yaml -p community-templates --threads 20 --keepfolders[INF] reading config: repos.yaml (46 repositories)[INF] cloning with 20 threads, keeping .yaml onlycommunity-templates/cves/2023/CVE-2023-27350.yamlcommunity-templates/exposures/configs/exposed-env-file.yamlcommunity-templates/misconfiguration/http-missing-security-headers.yamlcommunity-templates/vulnerabilities/wordpress/wp-xmlrpc-pingback.yamlcommunity-templates/technologies/tech-detect.yaml[INF] deduplicated and saved 1,914 templates from 46 repositoriesguidance
Use cent to assemble a community-sourced nuclei template set before a scan. It gathers templates, it does not scan, so its folder output feeds directly into a nuclei -templates input. Run it ahead of nuclei whenever you want broader coverage than the default templates provide.
Runs the templates cent collects. cent is the upstream step that builds the expanded template directory it scans with.
Hunts GitHub for proof-of-concept exploits. cent specifically aggregates ready-to-run nuclei templates.
General GitHub content scraper. cent is purpose-built to clone and organize nuclei template repos.
faq
related
Import, export, and link workflow data with Airtable.
Decode Android APK files into smali sources and resources.
Check a file's values against conditions and exit with a matching code.
Extract all hosted zones from AWS Route53.
Output file lines by batch size, given START_LINE and END_LINE.
Extract a batch range from a file's lines or a folder's files, with parallel processing.
A config of template repos feeds cent, which clones them into one folder and hands it to nuclei so a scan with the expanded community set writes findings as a queryable output.
Facts on this page come from the live Trickest tool library.