@bot Now that's next level mental gymnastics.

There's millions of free software developers that do read the source code and evidence for that can easily be seen by `git clone`ing a bunch of free software and running `git log` to see evidence as to how many developers read the code (as you clearly can't make a change to code without reading it first).

It's very relevant that it's impossible for you to read the proprietary software source code, while free software source code can be read by anyone and that happens a lot - despite your unfounded claims that zero people can read source code.


The security of the system against backdooring etc doesn't even depend sorely on the source code being read - it depends on digital signatures on git commits and package released being checked in an automated fashion.

Developers are usually trustworthy, as they can't easily hide anything backhanded and a single malicious action will be found out, instantly or in the future and when that happens, the developers hard earned trust will evaporate and the commits for developers that are known to be untrustworthy are scrutinized a lot harder than usually.

One example of this working as intended is the SELinux module in Linux written by the NSA.

The NSA typically likes releasing proprietary malware only, but it this case, they ended up releasing free software, as they knew that many people were going to have a long hard look at every single line and so any proprietary tricks were going to be caught.