Giter VIP home page Giter VIP logo

www-project-code-review-guide's Introduction

OWASP Secure Code Review Guide

Contributions Welcome

Creative Commons License

Welcome to the official repository for the Secure Code Review Guide. The Secure Code Review Guide is a comprehensive guide that aids software developers in reviewing code for security vulnerabilities and security bugs.

We are currently working on a new release (3.0), and our project is open for contributions. Have a look at the discussion folder to see how the project is shaping up and read about the roadmap and vision.

To find the previous code review guide 2.0 here.

How to contribute

The new release of the secure code review guide has just started, and as such, it's a fantastic time to join us and help shape the latest version. We welcome your contributions, whether you have a lot or just minimal experience in software engineering, security, or IT. We are happy to help you get started. Similarly, if you have a lot or just a little time at your hand, there are plenty of opportunities to help with this project.

Here are a few ways you can help:

  • Please help us fix any spelling mistakes or grammatical errors in the current draft.
  • The code review guide is only available in English, but it would be great if you could help translate it to another language.
  • We have a list of open issues from which you can pick one to work on and submit a pull request. If you need help with getting started, please get in touch.
  • Finally, if you have an excellent idea for improving the code review guide, you can also open a new issue yourself.

Get in touch

You can find us on Slack:

  1. Join the OWASP Group Slack with this invitation link.
  2. Join this project's channel #project-secure-code-review-guide

Feel free to ask questions, suggest ideas, or share your best recipes.

www-project-code-review-guide's People

Contributors

duncanwd avatar hblankenship avatar hummus-ful avatar kingthorin avatar mgreiler avatar nanzggits avatar owaspfoundation avatar techwritegirl avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

www-project-code-review-guide's Issues

Create discussable outline from code review guide 2.0

Create a markdown document that covers the outline of the secure code review guide 2.0, and also has a discussion and decision section for each chapter/section/part.

This should guide our discussion on what to keep, adjust and remove from the 2.0 to the 3.0 version.

Investigate unknown/unclear sources for information presented in previous Guide 2017

In the previous guide (2017), which can be found here https://owasp.org/www-project-code-review-guide/assets/OWASP_Code_Review_Guide_v2.pdf, are several graphs and very interesting statements and facts that do not have proper attribution of source.

For example, in Figure 1, a survey result that is only very briefly mentioned is depict. The quality of this source, and its legitimacy needs to be investigated. Based on what the investigation finds, we either will keep, remove or update the information for the upcoming version of the guide.

image

Information and statements that are hard to judge given the information in the guide can be found throughout. Each one of those has to be investigated and evaluated for future-fit in the updated/new guide.

Each piece of information that needs to be investigated and evaluated should probably become its own issue. This issue can serve as a "parent" issue.

Add readme file for potential contributors

Add a readme that explains

  • the purpose and goal of the guide
  • the current state it is in
  • how to contribute to the project.

We also have to make sure the readme is not part of the deployment process.

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.