Most software engineers aren’t qualified to have an opinion about the quality of proprietary safety critical software systems that also happen to run against proprietary hardware.
So unless you’ve found an economical way to develop an open source jetliner... honestly, what would be the point of open sourcing safety critical systems to the general public?
I’m not at all saying it should be closed off from external safety inspectors or regulators or anything like that, but I’m not really seeing the value of opening the software up to the general public.
You'd be surprised what fraction of a safety critical codebase is just mundane code that anybody can understand with the same amount of effort it takes for "normal" software. The real problem is that most outsiders don't understand the requirements very well (unless you make them public too!), so they can likely only find "simple" code quality issues.
That’s essentially my point. Just finding simple code quality issues isn’t going to cut it, especially when you need hundreds of thousands of dollars of hardware to even test the code against.
I still really just don’t get where you’re going with this. You’d need hundreds of thousands of dollars worth of hardware to even test these kinds of software systems.
Simply reading the code isn’t going to help you find critical safety flaws.