Red Crow Add-on Primer
redcrowsolution.com/how-to-vet-a-browser-extension/
Vetting

How to Vet a Browser Extension Before You Install It

Five minutes of looking in the right places tells you more than the star rating ever will.

Start with whether you need it at all

Every extension is a piece of someone else's software running inside your browser. The safest one is the one you did not install. Before vetting anything, check whether the browser already does the job. Reading modes, screenshot tools, password storage, tab search and translation have all moved into the browser itself over the years, and a built-in feature brings no new author to trust.

If you still want the add-on, the checks below run from quickest to slowest. Most poor candidates fail one of the first three.

Get it from the browser's own store

Install only from the add-on store run by the maker of your browser, reached through the browser's own menu. Stores review submissions and can remove an item from every user's browser when it turns out to be harmful. That review is imperfect, but it is a filter, and a file handed to you by a pop-up or an email has passed no filter at all. Be wary of search results that lead to look-alike listings; opening the store from the browser menu and searching there avoids the problem.

Find out who made it

A listing names a developer. Look for a working website, a way to contact a human, and some sign that the author exists outside this one listing. A long-standing project with a public history is easier to trust than a name that appeared last month with nothing behind it. If the code is published as open-source software, that is a mild plus: you probably will not read it, but others can, and authors who publish their code tend to expect to be checked.

Copycats are common. A popular tool attracts imitations with nearly the same name and icon. Compare the developer name on the listing with the one on the project's own website before trusting a familiar-looking logo.

Read the reviews the right way

Skip the average score. Sort reviews by most recent and read the low ones first. You are looking for specific complaints: "started showing ads after the last update", "now asks to read every site", "changed my search engine". Those describe behaviour, and behaviour is what matters. A wall of short, similar, glowing reviews posted close together is not evidence of quality and can be evidence of the opposite.

Check the date of the last update too. An extension untouched for years may simply be finished, but it may also be abandoned, and abandoned tools break quietly or get picked up by new owners.

Read the privacy section, briefly

Stores ask developers to declare what data they collect, and many link to a privacy policy. You do not need to read all of it. Search the page for three words: "collect", "share" and "third". The sentences around them tell you what leaves your browser and who receives it. A tool that changes fonts and also collects browsing activity "to improve our services" has told you how it earns its keep.

Absence is information as well. A tool with wide access and no policy at all has declined to make any promise, which means there is no promise to break.

The five-minute check
  1. Could the browser already do this?
  2. Is it in the browser maker's own store, found from the browser menu?
  3. Is there a real, reachable author?
  4. What do the newest low reviews complain about?
  5. Do the requested permissions fit the job, and does the privacy section say what is collected?

Know what you are guarding against

Outright malware in an extension store is the dramatic case, and stores do catch a good deal of it. The more ordinary risk is duller: a tool that works as advertised and also gathers your browsing activity, inserts its own referral codes into shopping links, or swaps your default search page. None of this breaks your computer. It simply turns your attention and your data into someone's income without a clear statement that this is the deal.

That is why the checks above lean on fit and candour, and less on technical inspection. You are not trying to audit code. You are trying to decide whether this author has been straight with you about what the tool does and how it is paid for.

After installing

Vetting does not end at the install button. For the first few days, notice whether anything else changed: new tabs you did not open, a different search page, extra banners on sites that had none. If something feels off, disable the newest extension first and see whether the oddity stops. Disabling is instant and reversible, so there is no cost to testing a suspicion.

Finally, keep the total small. Each additional extension adds another author, another update stream and another set of permissions to keep track of. A short list you understand beats a long list you have forgotten.

Written by Freya Calderwood · last built 2026-11-16