v1.3.3

What's Changed

• Validate fix err by @xm1k3 in #68

Full Changelog: v1.3.2...v1.3.3

v1.3.2

What's Changed

• Validate fix 2 by @xm1k3 in #67

Full Changelog: v1.3.1...v1.3.2

v1.3.1

What's Changed

• Validate fix by @xm1k3 in #64
• Revert "Validate fix" by @xm1k3 in #65

Full Changelog: v1.3.0...v1.3.1

v1.3.0

Validate feature added

The validate command, adopted from the ProjectDiscovery's Nuclei project, is a crucial feature in the application's toolkit. It specializes in validating templates. When executed, it scans a specified folder for YAML files. Each YAML file is checked for validity. If a template is found to be invalid, it is promptly removed from the folder.

cent validate 
cent validate  --path <folder_path>

Example

Suppose you have a folder named templates with the following files:

• template1.yaml (valid)
• template2.yaml (invalid)
• template3.yaml (valid)

cent validate --path ./templates

After execution,template2.yaml(invalid) will be deleted.

What's Changed

• Update README.md by @numaan911098 in #50
• solve issue #43 by @xm1k3 in #53
• Update 301 links by @szybnev in #54
• Fix bug in copying files by @xm1k3 in #57
• Validate command by @xm1k3 in #58
• Validate command multithread by @xm1k3 in #59
• Documentation by @xm1k3 in #60
• Update version.go by @antonydevanchi in #62

New Contributors

• @numaan911098 made their first contribution in #50
• @antonydevanchi made their first contribution in #62

Full Changelog: v1.2...v1.3

v1.2

Summary feature added

Flags:
  -h, --help          help for summary
  -p, --path string   Root path to save the templates (default "cent-nuclei-templates")

Usage

cent summary

output:

+-------------------------------+-----------------+
| TEMPLATES TYPE                | TEMPLATES COUNT |
+-------------------------------+-----------------+
| CVE Templates                 |           21981 |
| Other Vulnerability Templates |           16779 |
| Total Templates               |           38760 |
+-------------------------------+-----------------+

Issues

• Issue: #48 by @szybnev

cent version v1.1

Check feature

cent check --help

Check if templates repo are still available

Usage:
  cent check [flags]

Flags:
  -h, --help     help for check
  -r, --remove   Remove from .cent.yaml urls that are no longer accessible or are currently private

Global Flags:
      --config string   config file (default is $HOME/.cent.yaml)

Test yaml

...
...
community-templates:
  - https://github.com/joanbono/nuclei-templates
  - https://github.com/0xPugazh/my-nuclei-templates
  - https://github.com/1in9e/my-nuclei-templates
  - https://github.com/5cr1pt/templates

Command

cent check --config .cent.yaml -r

Output

[ERR] URL https://github.com/joanbono/nuclei-templates  Status code: 404
[SUCCESS] URL https://github.com/0xPugazh/my-nuclei-templates Status code: 200
[SUCCESS] URL https://github.com/1in9e/my-nuclei-templates Status code: 200
[SUCCESS] URL https://github.com/5cr1pt/templates Status code: 200

Updated yaml

...
...
community-templates:
  - https://github.com/0xPugazh/my-nuclei-templates
  - https://github.com/1in9e/my-nuclei-templates
  - https://github.com/5cr1pt/templates

cent version 1.0.1

• bug fixes

cent version 1.0 (stable)

Big news:

• cent now removes duplicated templates!
• Better performance
• cent version command added
• Dramatically increased the speed that the repositories are cloned by adding concurrency. You can set the number of workers by using the -t flag.

cent version 0.4

• Better performance
• Better readme
• Removed -n --name flag, now you can use -p --path for everything
• New nuclei templates repos added in readme.md

cent version 0.3

• Added init command, the user no longer has to copy and create the .cent.yaml file, it is done automatically by cent now (cent init)
• New nuclei templates repos added in readme.md