Backup_Repos/SecLists
1
0
Fork 0
mirror of https://github.com/danielmiessler/SecLists synced 2026-05-07 12:05:30 +02:00
Code Issues Projects Releases Wiki Activity

feat(docs): Updated contribution guidelines

Browse source
This commit is contained in:
ItsIgnacioPortal 2026-04-17 20:05:00 -03:00
parent 2179ef697e
commit 50818f3bb3
No known key found for this signature in database
GPG key ID: 8A401781634614F8
1 changed files with 8 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

9
CONTRIBUTING.md
View file

@ -12,7 +12,7 @@ Significant effort SHOULD be made to give attribution for these lists whenever p
## Wordlist content
If you're uploading a new Wordlist, make sure to follow these guidelines.
If you're adding new content to a wordlist or creating a new one, make sure to follow these guidelines.
### Remove leading slashes
Do not include leading slashes in the wordlists contents. This ensures all SecLists wordlists have the same format, and also helps keep the wordlist filesize down.
@ -47,6 +47,13 @@ For example:
- ✅ `path/to/auth?password={PASSWORD_PLACEHOLDER}`
### Remove in-file comments and put them in the documentation
Most users of SecLists expect the wordlists to be ready to use unless otherwise stated. For that reason, wordlists should never contain comments such as lines beginning with `//` or `#` for the purposes of commentary.
If certain content within the wordlist requires an explanation, it's recommended to place those explanations in the `README.md` of the relevant directory, along with any other relevant explanations (such as placeholders).
## Folder naming scheme
Folders should be named with the train case scheme, for example `File-System`.