2 ms·
Well, you can inspect the entirety of the plugin code yourself. While they could of course update it with something bad, there is nothing inherently hidden from
by k3n 13y ago
Well, you can inspect the entirety of the plugin code yourself. While they could of course update it with something bad, there is nothing inherently hidden from you that I'm aware of.
- pachydermic 13y agoReally? Where can you find the source code? I never noticed it on their site - seems like they're a typically closed-source company to me. Am I missing something obvious?
- k3n 13y agoLots of ways! First and easiest would be to simply 'inspect popup' on the icon, and then navigate to the sources tab, though you may not get all of the code this way (perhaps if it was conditionally/dynamically loaded). Second way, and probably the best, would be to go to its store page, and in the URL will be the extension ID; for Ghostery, it's "mlomiejdfkolichcflejclcbmpeaniij". Now, just find that in your Chrome installation directory, e.g. for Win7 the extension would be located at %LOCALAPPDATA%\Google\Chrome\User Data\Default\Extensions\mlomiejdfkolichcflejclcbmpeaniij\. The last way would be to intercept or otherwise directly down the .crx file (curl, wget, etc.), which is just a compressed zip archive. You can do the same for FF extensions as well, those .xpi files are just zip files.
- pachydermic 13y agoMan, I don't know. That's not open source - they don't seem to intend for you to easily be able to see and understand the code. There's less peer review that way. They're also an ad (analytics?) company. I just don't trust them.