Memory-Safety
Memory-Safety copied to clipboard
ossf
Publish a guide on interfacing between memory safe by default and non-memory safe by default languages Some initial drafts: - https://github.com/ossf/Memory-Safety/blob/main/docs/best-practice-interfacing.md - https://www.swift.org/documentation/cxx-interop/ (Swift C++ interop, reference provided upon request)
Add to [best-practices-interfacing.md](https://github.com/ossf/Memory-Safety/blob/main/docs/best-practice-interfacing.md)
Add to [best-practices-interfacing.md](https://github.com/ossf/Memory-Safety/blob/main/docs/best-practice-interfacing.md)
Add to [best-practices-interfacing.md](https://github.com/ossf/Memory-Safety/blob/main/docs/best-practice-interfacing.md)
To the [best-practice-memory-safe-by-default-languages file](https://github.com/ossf/Memory-Safety/blob/main/docs/best-practice-memory-safe-by-default-languages.md)
Ideas * Tutorial on how to use copilot-instructions.md with memory safety instructions * Best practices for converting memory unsafe code to memory safe code using LLMs
# Memory Safety Scorecard Proposal The larger discussion on this is in [Scorecard #3736](https://github.com/ossf/scorecard/issues/3736). However, I'd like to start an issue within this repo to discuss this as a SIG...
The purpose of this initiative is to explore the necessity for supplementary guides to accompany the [C/C++ Binary Hardening guide](https://github.com/ossf/wg-best-practices-os-developers/tree/main/docs/Compiler-Hardening-Guides) in other programming languages. Our intention is to examine compilers...