Well, you can always go with the JSON license[1] ("The Software shall be used for Good, not Evil."), though there are 2 things: - This license is only open sou

Well, you can always go with the JSON license[1] ("The Software shall be used for Good, not Evil."), though there are 2 things: - This license is only open source in spirit, but technically not really due to this restriction. - who defines what is malicious? The mouse thinks the cat is a monster, but the cat is only playing catch with a self-moving fur ball... Alternatively you can go the Red Hat way: the GPL license says that the source should be distributed along with the binary. If you don't distribute the binary of your application, you don't have to give the source to anyone. Red Hat gives the binary to its subscribers (friends), along with the source. If they see that one of their customer has leaked the source, the contract can be terminated. One might be inclined to ask however how much is it different from a closed source distribution model. [1]: https://www.json.org/license.html https://www.json.org/license.html