endo

I used E in the 90s: http://erights.org/ I haven't kept up with newer systems but I've heard of https://github.com/endojs/endo and just came across http://reports-archive.adm.cs.cmu.edu/anon/home/anon/isr2017... (which says "in the style of the E programming language" -- that's as far as I've read) while looking that up. WebAssembly was designed to follow the same capability security principles. CHERI too as someone else just brought up. Yet another newer capability system in progress -- I don't know what it can do today or if it tackles this particular problem but it sounds cool: https://spritelyproject.org/

I don't know why you are being silently downvoted, as I think it is worth talking about the potential of using static analysis to improve things. One promising approach is Endo[0] which "uses LavaMoat to automatically generate reviewable policies that determine what capabilities will be distributed to third party dependencies." [0] https://github.com/endojs/endo