Conversation

The Librem 5 and Pinephone are closed hardware with closed firmware. The complexity in the entirely closed source SoC and other hardware components / firmware completely dwarfs the complexity in userspace libraries. You're also grouping things that are open source in with blobs.
2
You think wpa_supplicant and all of the other largely open source code in vendor is closed source? Lack of interest from people in building code from source let alone replacing the closed source components (many of which have working open source alternatives already) says a lot.
1
You're inaccurately treating the division of code into the vendor image as being based on open vs. closed source. It isn't and a device with fully open drivers has everything involved in device support contained to the vendor image. You're confusing Pixel issues with AOSP issues.
1
The proprietary code in userspace can be inspected/audited (it even has symbols), fuzzed and hardened with a subset of the techniques used elsewhere. This is about ideology, not so much privacy or security, especially when the far more complex SoC underneath is closed either way.
1
That code is not obfuscated and has debug symbols. You get all the function names, etc. even though you don't get the source code. It's not a black box. In reality it's not really any harder to inspect it for backdoors than any of the open source code. People don't do either.
1
The Librem 5 and Pinephone are not open hardware targets though. Librem 5 is even closed in ways that the Pixel hardware is not. Pinephone at least doesn't do destructive things making things substantially worse to play stupid semantic games to get a meaningless certification.
2
1