Responsibility of source code&#39;s copyright owner
<p>Let’s assume that author makes source code of program publicly available. Every file has single-line copyright header “Copyright (c) &lt;Owner&gt;. All rights reserved,”. Nothing is explicitly allowed; no rights are explicitly granted.</p>
<p>Is it possible to sue &lt;owner&gt; if something wrong with the program? Does it make sense to add standard warranty disclaimer “software provided as-is...”?</p>
<p>Is it going without saying: if nothing is allowed, then no warranties are provided?</p>
<p>Update:</p>
<p>For context: I'm author of the source code, I'd like to make code available for inspection purposes, protect myself from any possible legal risks, and don't put huge effort\resources on writing full-fledged proprietary license agreement. This is temporary approach and I don't have expertise to write any legal documents myself.</p>

<p>When the question is &quot;is it possible to sue X over issue Y?&quot; the answer is always &quot;Yes&quot;. Anyone can sue over almost anything, and some people will. Some suits have almost no chance of success, adn some will be dismissed promptly. But even so, they can cause trouble and some expense for the defendant.</p>
<p>In this case, it seems that the developer, who is also the copyright holder, has granted others the right to read the source code, but not to download it or run it. The developer (whom i will call D) has not asserted that the code successfully performs any particular function, and has not sold or delivered it to any particular customer or user.</p>
<p>None the less a reader R does download the code, compiles it, and runs the resulting binary, thereby arguably infringing D's copyright. R finds the code not to work as R had expected, and R sues D for damages on an implied warranty theory. Could R win such a suit?</p>
<p>Well this may depend on the particular laws of the country or jurisdiction where R brings suit, and the question does not specify that.,</p>
<p>In the US one possibly relevant law would be the <a href="https://www.findlaw.com/consumer/consumer-transactions/warranty-laws-and-the-magnuson-moss-warranty-act-.html" rel="nofollow noreferrer">Magnuson-Moss Warranty Act of 1975</a> ut this act applies only to &quot;written warranties on consumer products costing more than $10.&quot; As D makes no charge for the code, and provides no warranty at all, the Act weill not apply to D.</p>
<p>The page <a href="https://www.jonesday.com/en/insights/2018/08/be-wary-of-warranties-for-software-design" rel="nofollow noreferrer">&quot;Be Wary of Warranties for Software Design &quot;</a> from Jones Day discusses the  California Commercial Code and the Song-Beverly Consumer Warranty Act. The Act imposes an implied waranty if there is any express waranty. The page reads:</p>
<blockquote>
<p><strong>Implied Warranty of Fitness for a Particular Purpose</strong><br />
This implied warranty comes into play when the software supplier knows of the buyer's particular purpose for purchasing the software and knows that the buyer is relying on the supplier's skill and judgment to provide suitable software.</p>
</blockquote>
<p>Since there is no purchase here, this does not seem to apply.</p>
<p>The Jones Day page also reads:</p>
<blockquote>
<p><strong>Implied Warranty of Merchantability</strong><br />
This implied warranty, as its name suggests, promises that the software meets the standards of performance expected by merchants in the trade. Again, this implied warranty turns on industry standards and practice. Suppliers can disclaim this implied warranty or agree with purchasers to particular terms that will supersede it.</p>
<p><strong>Disclaimer of Implied Warranties</strong><br />
Unless prohibited by the Act, the Code allows sellers to disclaim any express and implied warranty. Software suppliers may decide to provide a limited, exclusive, and express warranty (such as meeting a particular specification or industry standard) and then disclaim all other warranties. Disclaimers must be specific and conspicuous; state law and practice provides the important language and format for disclaimers. If the Act applies to a transaction, for example, the disclaimer must say that the goods are sold &quot;as is&quot; or &quot;with all faults.&quot;</p>
</blockquote>
<p>I see no obvious legal theory on which a suit for an implied warranty could be successful against D, but I have no way to know what  provisions the law of R's jurisdiction might have.</p>
<p>Including a disclaimer such as:</p>
<blockquote>
<p>This code is posted for demonstration and discussion only. No right to download and run it has been granted. It is provided &quot;as is&quot;. The author makes no assertions as to its performance or effects if run, provides no warranties of any kind, and disclaims any implied warranties.</p>
</blockquote>
<p>costs nothing and might deter some people from filing suits, even if such suits are unlikely to prevail.</p>

copyright licensing