-
Updated
Oct 20, 2020 - Makefile
safety
Here are 287 public repositories matching this topic...
-
Updated
Nov 8, 2020 - PHP
-
Updated
Jun 9, 2020 - JavaScript
-
Updated
Oct 30, 2020 - Go
This issue was created from results of the Security Assessment Improvement Working Group (cncf/sig-security#167 (comment)).
Security Assessment Process Mechanics Improvements
Premise
- There are several points of mechanical improvement to the security assessment process. This issue encapsulates the brainstormed ideas around various aspects of the
-
Updated
Sep 27, 2020
-
Updated
Nov 5, 2020 - PHP
-
Updated
Nov 6, 2020 - PHP
-
Updated
Aug 2, 2020 - Python
-
Updated
Nov 8, 2020 - HTML
-
Updated
Nov 2, 2020 - C++
-
Updated
Feb 10, 2020 - Python
-
Updated
Jul 29, 2020 - Swift
-
Updated
Apr 16, 2020 - Python
-
Updated
Aug 27, 2020 - Ruby
-
Updated
Jan 7, 2018 - Rust
-
Updated
Jul 10, 2019
There is a need to create the landing page for the project for people to easily understand the project.
We intend this to be a beginner friendly issue. Anyone with basic knowledge in HTML , CSS , JS can take up this issue. A basic webpage with a good theme and design is required.
The landing page should include :
- Mission and vision of the project
- Description about the project
- Con
-
Updated
Oct 16, 2020 - Swift
-
Updated
Jan 3, 2019 - D
-
Updated
Jul 14, 2020 - TypeScript
-
Updated
Feb 5, 2018 - Python
-
Updated
Nov 3, 2017 - C#
-
Updated
Apr 16, 2020 - Python
Improve this page
Add a description, image, and links to the safety topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the safety topic, visit your repo's landing page and select "manage topics."


#196 introduced a double up of each entry that wasn't caught in review. In order to prevent repeat cases of this, or minor double ups, a Github actions entry should be created that checks for any double ups of the program name at the time when a new pull request is created, and if so, fail the case.