> most uses of unsafe would also require explicit whitelisting. I think this is probably where all proposed whitelist/capability proposal discussions end. It's

> most uses of unsafe would also require explicit whitelisting. I think this is probably where all proposed whitelist/capability proposal discussions end. It's going to be too many crates that are in that category for it to be useful. A good first step (not sure if it's already taken tbh) would be to at least sandbox build execution. So that an attacker can't execute arbitrary code when your app is compiled.