7 ms·
You can unpack and view the code of any extension after you've installed it. There's even a rule against obfuscation, though I'm not sure how enforced that is.
by timabdulla 2y ago
You can unpack and view the code of any extension after you've installed it. There's even a rule against obfuscation, though I'm not sure how enforced that is.
A Chrome extension is basically a zip archive with a bunch of JavaScript inside. There's no safeguarding of the code within.
- Raed667 2y ago> There's even a rule against obfuscation Does that only cover the background/web-worker or does it also include the UI parts (popup, content-ui, dev-tools...) ? That would make using something like React or Vue almost impossible.
- timabdulla 2y agoThere's no rule against minification, which I assume is what you're referring to when you say it would make using React or Vue impossible. There's a difference between minification and obfuscation, but again, I'm not sure how they adjudicate it or how much they enforce it.
- hysan 2y ago> There's even a rule against obfuscation This is definitely not enforced. I’ve downloaded multiple extensions in the past when I wanted to learn how they worked. All of them were obfuscated. edit: saw the below comment and editing before this gets questioned. I’m not talking about minification. It was definitely obfuscation.