That's my impression too (see my other comment). Each package published to Deno could come with a set of declared permissions (similarly to Android apps). Whe

That's my impression too (see my other comment). Each package published to Deno could come with a set of declared permissions (similarly to Android apps). When importing the package in a module, Deno should detect that permissions scoped at current module level are wider than what the package requires, and automatically narrow down the list of authorized calls. This would probably be very costly. Suppose that I'm importing a function from lodash (that requires no permissions) and my module calls it repeatedly while also accessing the file system...