I'm not about to install that extension and find out myself as that could cause some... serious problems... but that was my first thought as well. What's to stop this from doing something nefarious? Its sandboxing privileges are not remotely clear from what's in the app store, and I don't see of any reasonable way to contain what it can and cannot do.
Granted this is equally a problem with any terminal emulator that you didn't compile yourself after examining the source code, but I have quite a bit more faith in Apple and the various Linux repo maintainers than some random guy publishing to the chrome app store. I don't know if Google even claims to vet its contents, but if they do I know they do a terrible job because I've ripped open some extensions to confirm they're doing some sketchy stuff (nothing insecure or worrying, more like adding affiliate links to your entire browsing experience)
Not only that, it's an official part of our Oncall toolkit. I've got coworkers for whom a chromebook is now the primary (and only) laptop, even when oncall.
Nothing that matters; Everyone needs to carry around their corporate laptop, one-time-password token, and have configured VPN and ssh clients. The rest varies by team and job role.
I've been using this for quite some time, and there are basically two use-cases: a)alternate to putty for windows and b)an actual shell in your browser (You press Alt+1 instead of Alt-tab).
Granted this is equally a problem with any terminal emulator that you didn't compile yourself after examining the source code, but I have quite a bit more faith in Apple and the various Linux repo maintainers than some random guy publishing to the chrome app store. I don't know if Google even claims to vet its contents, but if they do I know they do a terrible job because I've ripped open some extensions to confirm they're doing some sketchy stuff (nothing insecure or worrying, more like adding affiliate links to your entire browsing experience)