More than a few people are saying, and in more than a few places I am reading, that Chrome browser has no vetting process for its extensions. How could this be possible, especially for a browser known for its security-awareness and features? The thought of Chrome not having a vetting process for extensions absolutely floors me, yet the more I search for info on that subject, the more I encounter what some Wilders members have been saying... there is no vetting process. I started to delve into this on another thread recently, but have since decided the topic deserves its own space. The most substantial info I have read so far regarding the existence of a Chrome extension vetting process actually came via an email I received a few months ago from a Google Developer Advocate and member of the privacy team, Mike West. I had emailed Mike about a Chrome Privacy article he's written, and I asked if he was referring to the Chrome extension vetting process in any part of his article? The reply came back that he was not. He stated that my question was more appropriate for the security team, but he did say this much about the vetting process for extensions... Now, I know Mike's response isn't very detailed, and perhaps not conclusive, but in my opinion, it does at least counter the "no vetting process" statements that seem to prevail everywhere about Chrome extensions. So, I'd like to know, what have you learned about this process? Is the open source aspect what Chrome devs are banking on for vetting? How can I get more details on this subject? Are other Chrome users (or observers) amazed at the possibility that there is no extension vetting process? I did come across one review (of sorts) that is floating around out there under various reincarnations, that does reference the process, by saying... I've seen this repeated in at least a couple places, such as here and here. I have emailed both of these sources and asked them to share with me where they came up with the "basic vetting process" info. No replies as of yet. Any comments or contributions to this topic will be appreciated.