Allow package based permission scoping

[swcarter007]

I'm running into an issue trying to balance security and ease of use. In my case, I have a particular library I'm attempted to use @google-cloud/secret-manager. I'm also attempting to define the net security permissions on the application when running to limit outbound calls to known domains. The problem I'm running into is that the particular SDK is doing a few things that require some specific outbound calls to IP addresses. The feature request I'm looking for would be the ability to granularly define permissions based on the library using that particular permission.

Perhaps some structure like this

{
  "permissions": {
    "libs": {  // special global property to identify its not a normal permission
       "@google-cloud/secret-manager": {
         "net": true
      }
    },
   "default": {
      "net": [] // some restricted list by default
    },
    "dev": {
       "libs": {
          "@google-cloud/secret-manager": {
                    //special override when using the "dev" permission 
           }
       }        
     }
  }
}

The reason why I think this could be a reasonable use case is because sometimes there are libraries that you can trust more than others, so you may want to specify permissions slightly differently for those libraries compared to more unknown libraries.

[stefnotch]

I believe that the last time this was brought up it was shot down on the grounds of not actually being securely implementable. Instead sandboxing with web workers was recommended.

const worker2 = new Worker(
  new URL("./worker.ts", import.meta.url).href,
  {
    type: "module",
    deno: {
      permissions: {
        read: [
          new URL("./file_1.txt", import.meta.url),
          new URL("./file_2.txt", import.meta.url),
        ],
      },
    },
  },
);