Comment by wizzwizz4

It depends: having it notarized is a way to show someone with a certain reputation of "Hey! This is my code, this is me, if something happens, you can kill the switch".

If notarisation requires you some kind of payment, I would be okay with you charging me some money, if I obviously find your code has a good value for me.

I read comments around here about "Well: you can compile it yourself" or "it's open source! You can check the code by yourself".

And, while all of those arguments are accurate and valid, the point is "I do not feel like it" or, a little reminder, "The Great Suspender" was an example of a beautiful open source little app to suspend tabs on Google Chrome that, one glorious day, switched hands and, suddenly, after some time, someone noticed the repository and the code from the add-in were different, and those changes were made with nefarious intent.

Luckily, somehow found out, but some people do not have the time or the will to be playing that game.

A piece of code that requires access to my camera, regardless of size (<1000 lines of code) or build, it's something I just don't put on my computer without thinking it twice.

Thank you for the tone: I hope I responded to your question :)

I seriously doubt that he actually would. And in that unlikely event he'd be in a miniscule minority. Not a good open source monetisation strategy.