By looking at the press headlines, we've learned that open source is already being used in space applications that have safety considerations today. Details about the safety analysis performed are behind NDAs and are not available to developers in the open source projects being used. To make the challenge even more interesting, the processes the safety standards are expecting are behind paywalls, and not readily accessible to the wider open source community maintainers and developers. Figuring out pragmatic steps to adopt in open source projects, like the Linux kernel, requires the safety assessor communities, the product creators, and open source developers to communicate openly. There are some tasks that can be done today that help, like knowing exactly what source is being included in a system and how it was configured and built. Automatic creation of accurate Software Bill of Materials (SBOMs), is one pragmatic step that has emerged as a best practice for security and safety analysis. There are also other different practices that various open source projects are adopting that can help with the safety analysis. This talk will overview some of the methods being applied in different open source projects, as we try to establish other pragmatic steps that will help to solve this challenge.