Georg Kunz

Hi all, we are actually very interested in picking this up and contributing to the document. I'll invite one of our security guys, who has worked on a similar document,...

Hi @SecurityCRob, what do you think about putting this topic on the agenda for the next meeting? I'd like to bring a colleague who is interested in contributing content to...

Great, thanks!

Hi @torgo! Are you still interested in getting this in? I support the idea but would ask for incorporating @david-a-wheeler's suggestion.

Below are the scan results showing the current state of the repository. Low hanging fruits seem to be * addition of a SECURITY.MD file, * configuration of GITHUB_TOKEN permissions, *...

Below is a scan result of the current state of the repo: Low hanging fruits seem to be - addition of a SECURITY.MD file, - configuration of GITHUB_TOKEN permissions, -...

Hi all, thank you for evaluating the findings and recommendations by ScoreCard. As shown above, a three recommendations have been adopted in the meantime: - adding a security policy file,...

Hi @myteron, all very good input. It seems, we may want to address some of these points individually. I'd rather leave writing about the purpose to you as the driver,...

@myteron, great. Thanks for the update. Regarding the tables and their width: This is really low priority and just something I noticed. In general, the project members can of course...

Jekyll is run under the hood by GitHub when rendering the current guides. I run a test using my fork: - Code: https://github.com/gkunz/wg-best-practices-os-developers/blob/0afa4264397698051ee0be84f219a34cf73c8f46/docs/Secure-Coding-Guide-for-Python/CWE-664/CWE-134/README.md?plain=1#L19 - Resulting render (notice that the first...