No, the absence or presence of a digital signature without knowing the context does not mean that you automatically trust or distrust the executable.
If there is a valid signature, you know that the file was released by the signer and that it was not modified afterwards. But you still have to decide if you trust that signer.
For example, a valid digital signature does not mean that the executable does not contain adware. There are some download sites that bundle adware with their installation programs, and then sign them.
The absence of a digital signature doesn't mean you have to distrust the file. There are many developers who don't have the money to buy a code signing certificate.
The reason why I mentioned digital signatures in your other post, is that you seemed to trust the developer, but were not sure if a third party had tampered with the file.
The presence of a digital signature by the developer means that the file was not modified by somebody else.
SANS ISC Handler
Microsoft MVP 2011-2016 Consumer Security, Windows Insider MVP 2016-2018
If you send me messages, per Bleeping Computer's Forum policy, I will not engage in a conversation, but try to answer your question in the relevant forum post. If you don't want this, don't send me messages.
Stevens' law: "As an online security discussion grows longer, the probability of a reference to BadUSB approaches 1.0"