There's no one example. It's just something that crosses my mind every time I see a sourceless executable distributed here lately.
User assurance of safety is important, especially as IT security has become an increasingly concerning issue in recent times.
Big problem. A homebrew dev might have legit reasons for not releasing source – equally legit are the users' reasons for wanting the source before trusting.
I might take the risk of bricking a console forever (because of closed source software turning out to be destructive malware) and will volunteer if a test is needed.
Still people use Windows, iOS, Android phones with locked bootloaders and unavailable kernel/driver sources… everyday for their personal life and for business. The implications of banks relying on people accepting "Google Terms of Use" and demanding the usage of software that cannot be revised independently for security reasons hits me much harder. I simply refuse to trust such devices.
To be fair I'm unable/never built an OS from source and surely aren't remotely able to verify e.g. the kernel source of "5.3.18-150300.59.49-preempt #1 SMP PREEMPT Mon Feb 7 14:40:20 UTC 2022 (77d9d02) x86_64 x86_64 x86_64 GNU/Linux" running on the machine I'm typing on. Same for the "Firefox 91.5.0esr (64-bit)" which has GBAtemp open right now. And "KDE plasmashell 5.18.6". And all the other packages.
"Big problem. A homebrew dev might have legit..."
I mean, yeah, I can understand a dev may have a good reason to go closed, and that's why I'm not advocating anything near a full ban, just a plainly visible warning to educate the user that's there's increased risk when the dev won't disclose source.
It's not the movies or games downloads that I would worry about, like breaking into networks, downloading encrypted things, spying on network traffic. I have seen so many "Top Secret" seals on files when I was a kid
I was obsessed with finding UFOs, a surprising amount of US files where stashed on computers in other countries, China back in the early 90s omg sooo much