The very answer you linked states:
You don't need a EULA to protect yourself as a developer
Nevertheless, it's understandable that you're worried that a user could gain a copy and not accept the disclaimers of warranty and liability. I don't know if this would hold up in court if they did sue you under one of those things, but I can suggest a few licenses.
The Microsoft Public License begins with the preamble:
This license governs use of the accompanying software. If you use the software,
you accept this license. If you do not accept the license, do not use the
You could license your work under the Mozilla Public License. It states after its disclaimer of warrany in Section 6:
This disclaimer of warranty constitutes an essential part of this License. No use of any Covered Software is authorized under this License except under this disclaimer.
Or, the CeCILL states:
3.1 The Licensee shall be deemed as having accepted the terms and
conditions of this Agreement upon the occurrence of the first of the
- (i) loading the Software by any or all means, notably, by
downloading from a remote server, or by loading from a physical
- (ii) the first time the Licensee exercises any of the rights
"The rights granted hereunder" includes the right to use the software (Article 5.1). So they can't even receive a copy without accepting the Agreement.
Or, some non-licensing solutions:
- You could just provide an installer with an "I accept" button forcing the user to accept the FLOSS license. Admittedly, there's nothing to prevent them from hacking the installer if they really don't want to accept that, but how many people are going to do that?
- You could license pre-built executables under a proprietary license and provide the source code free of charge. This is a mean and extreme measure, but it will protect you wholly.