Thank you for considering contributing to the Web Security Testing Guide (WSTG)!
Here are some ways you can make a helpful contribution. The Open Source Guide for why and how to contribute is also a good resource. You will need a GitHub account in order to help out.
This project would not be possible without the contributions of writers in the security community! Our authors help to keep the WSTG relevant and useful for everyone.
Whether you are submitting a new section or adding information to an existing one, please follow the template example. The template sections are explained here.
When submitting your pull request, authors should link contributions to an issue:
- Open an Add New Content issue, or choose an unassigned new content issue and ask to be assigned to it.
- Create and switch to a new local branch with the name
new-<issue number>. For example,git checkout -b new-164.
Keeping the project up to date and looking spiffy is a group effort! The WSTG is a constantly updated document and benefits from your technical or editorial review.
When submitting your pull request, reviewers and editors should link contributions to an issue:
- Choose an open and unassigned issue to work on, or open an issue yourself. Post a comment in the issue and request to be assigned to it.
- Create and switch to a new local branch with the name
fix-<issue number>. For example,git checkout -b fix-88.
If you have expertise in any topic covered by the WSTG, your technical review is encouraged. Please ensure that articles:
- Follow the article template materials
- Follow the style guide
- Accurately describe vulnerabilities and tests
- Have appropriate and up-to-date inline links to resources
- Provide complete and relevant information suitable for an audience with basic technical expertise
Grammarians assemble! The WSTG welcomes your improvements in the areas of grammar, formatting, word choice, and brevity. All changes should adhere to the style guide.
Please don't hesitate to make as many changes as you see fit, especially if you notice that existing content does not match the article template materials.
Create an issue using the appropriate template.
Choose a short, descriptive title. Briefly explain what you think needs changing. Among other things, your suggestions may include grammar or spelling errors, or address insufficient or outdated content.
Here are the steps for creating and submitting a Pull Request (PR) that we can quickly review and merge.
- Set up your environment to fork the project and install a Markdown linter.
- Associate your contribution with an issue. To change existing content, read Become a Reviewer or Editor. To make additions, read Become an Author.
- Make your modifications. Be sure to follow our style guide.
- When you're ready to submit your work, push your changes to your fork. Ensure that your fork is synced with
master, then create a PR. You may want to allow edits from maintainers so we can help with small changes like fixing typos. - We'll review your PR. We may comment to ask for clarification or changes, so please check back in the next few days.
To increase the chances that your PR is merged, please make sure that:
- You've followed the guidelines above for associating your work with an issue.
- Your work is Markdown linted.
- Your writing follows the article template materials and style guide.
- Your code snippets are correct, well-tested, and commented where necessary for understanding.
Once the PR is complete, we'll merge it! At that point, you may like to add yourself to the project's list of authors, reviewers, or editors.
- Create an account on GitHub.
- Install Visual Studio Code and this Markdown linter plugin. We use this linter to help keep the project content consistent and pretty.
- Fork and clone your own copy of the repository. Here are complete instructions for forking and syncing with GitHub.