<p dir="auto">The project scope identifies that Deno aspires to be a "secure" runtime <a href="https://github.com/denoland/deno#readme">in the readme</a>.</p>
<p dir="auto">Lower on the page, an example is shown of loading code directly from a URL.</p>
<div class="highlight highlight-source-shell notranslate position-relative overflow-auto" dir="auto" data-snippet-clipboard-copy-content="deno run https://deno.land/std/examples/welcome.ts"><pre class="notranslate">deno run https://deno.land/std/examples/welcome.ts</pre></div>
<p dir="auto">loading resources only using a URL is notoriously insecure. Best practice for loading code using a URL is to use sub-resource integrity. This is because loading a URL could produce any code that will be run on your computer. And furthermore, there is probably no logging by default in Deno, so a malicious actor will take over your machine while also maintaining plausible deniability, which is 🆖.</p>
<p dir="auto">By default, please recommend that usage on the command line will require SRI. For example, that command could be.</p>
<div class="highlight highlight-source-shell notranslate position-relative overflow-auto" dir="auto" data-snippet-clipboard-copy-content="deno run https://deno.land/std/examples/welcome.ts 7353d5fcbc36c45d26bcbca478cf973092523b07c45999f41319820092b4de31"><pre class="notranslate">deno run https://deno.land/std/examples/welcome.ts 7353d5fcbc36c45d26bcbca478cf973092523b07c45999f41319820092b4de31</pre></div>
<p dir="auto">Furthermore, running Deno in this mode should reject any recursive includes from that above URL unless they do similarly include some SRI hash of what they are expecting to include.</p>
<hr>
<p dir="auto">If Deno does not wish to handle the case that a URL hosting code could change (i.e. you don't want SRI), then please update the README to say above that example:</p>
<blockquote>
<p dir="auto">WARNING: This example will run whatever code is at that URL in your Deno runtime. And because URLs can host any content at any time, changing without warning, even automatically based on your user agent, this approach is insecure and you should not trust it.</p>
</blockquote>
<p dir="auto">The project scope identifies that Deno aspires to be a "secure" runtime <a href="https://github.com/denoland/deno#readme">in the readme</a>.</p>
<p dir="auto">Immediately following, the first recommended install option is to use a shell code installer.</p>
<div class="highlight highlight-source-shell notranslate position-relative overflow-auto" dir="auto" data-snippet-clipboard-copy-content="curl -fsSL https://deno.land/x/install/install.sh | sh"><pre class="notranslate">curl -fsSL https://deno.land/x/install/install.sh <span class="pl-k">|</span> sh</pre></div>
<p dir="auto">shell code installers are notoriously insecure.</p>
<p dir="auto">In keeping with the "secure" project philosophy, please move this insecure installation option to below other options (indicating less preference) and add immediately above a note "shell code installers are less secure and this installation method is recommend only for continuous integration servers not having a concern for security".</p>