> one of the key issue with the Chrome store is that it allows extensions with ability to execute remote code in extension context
I agree. It is also "strongly recommended against" by the dev page [1]. Do you know a strong argument to allow usafe-eval? (i.e. what would be the rationale of continuing to allow it?)
[1] https://developer.chrome.com/extensions/contentSecurityPolic...