It’s time now to talk about one of the new features incorporated by Deno, something that Node.js never tried to tackle and that it would’ve prevented some of the major issues npm has had: security.
Even though they haven’t been that many, we’ve seen a few security issues creep up over the years with npm, and most of them related to the fact that any code executed with the Node runtime automatically has the same security privileges as the user executing the script.
In this chapter, we’ll see how Deno attempts to solve this problem by forcing users to specify which permissions to add.
