open-source-software licensing
Is written permission from the owner of unlicensed code sufficient for modification and usage without consequences?
<p>I recently found a repository on GitHub that I found quite interesting. I wanted to modify and use it in my project; however, the code is unlicensed. I proceeded to email the owner of the repository about it asking whether or not it was okay for me to use the code, and he gave me his permission to do so. Here is the conversation:</p>
<p>My email:</p>
<blockquote>
<p>Hi there! My name is Maraudery, I recently stumbled upon your repository, Sherlock, that happens to be implemented in Go. Recently I've been working on a program named GoSeek. It is an Open-Source Intelligence apparatus, basically an all-in-one OSINT tool/library. I noticed your repository isn't licensed so I thought I'd ask, how would you feel about me using the code, tweaking it a bit, and integrating it into GoSeek? Absolutely no pressure, I just thought I'd ask. If you are interested, check it out: <a href="https://github.com/maraudery/goseek" rel="nofollow noreferrer">https://github.com/maraudery/goseek</a> and feel free to email me back. :)`</p>
</blockquote>
<p>Their reply:</p>
<blockquote>
<p>Hi Maraudery,
You can change and use sherlock, feel free.
Thanks for reaching 🤗</p>
</blockquote>
<p>I just wanted to come here to make sure that I am not missing anything and I am able to proceed without suffering any consequences.Thank you for your time!</p>

<p>By &quot;unlicensed&quot; you mean that it doesn't state a license for use (MIT, GPL, etc.)? Those licenses are just a codified bundle of terms of use that cover many many edge cases. You have in place a much simpler agreement that covers the primary situation: you using/modifying the code for your own use.</p>
<p>It's just like borrowing a car. You will ask a friend &quot;hey, could I borrow your car for a bit?&quot; &quot;sure!&quot;. You know there's a possibility that you'll get in an accident or something weird will happen, but you think the chances of that are minimal and you would be able to work it out. If you ask a car rental company, they'll give you a full contract covering every situation that may happen. Similarly, a large company would be hesitant to borrow a car for corporate use without a legal framework surrounding it.</p>
<p>So you will likely be in the clear if you are just using it for a small project with minimal legal/financial implications. If you plan on turning your project into a multi-billion dollar empire, you should revisit your agreement.</p>

<p>Their reply <em>is</em> a license that allows you to &quot;change and use&quot; their software. We may conclude from the tone of the reply message that the original author has no interest to sue you, and I'd say cannot sue you successfully if you use this software in your own software.</p>
<p>Distribution is different. I don't think the answer gives you a license to sell 10,000 copies of your software with this software included. So if that's what you plan, you should contact the author again in the future and ask him whether he's Ok with what you're planning.</p>
