Analyse a Browser Extension's Permissions and Risk

Upload a Chrome, Edge or Firefox extension package and get a permission-by-permission risk breakdown: Host access, content scripts, remote code loading, external endpoints and the manifest settings that matter.

To get an extension's file: Use a CRX downloader for the store URL, or copy it from your browser profile's Extensions folder. Auditing extensions

Illustration of the browser extension analyzer in use

What this tool checks

9 checks across 1 areas. Each links to its reference page with the test, the risk and the fix.

Full reference

Extension permissions and behaviour

9 checks

The ones that most often decide the grade:

Guides for this tool

Background reading written to go with these results.

Frequently asked questions

How do I get the extension file?

Download it from the store with a CRX/XPI downloader tool, or export it from your browser's extensions folder. Firefox add-ons are .xpi files; Chrome and Edge use .crx.

Is 'access to all sites' always bad?

No. An ad blocker or password manager genuinely needs it. The question is whether the extension's purpose justifies it and whether the code does anything beyond that purpose.

What is remote code?

Code the extension downloads at runtime instead of shipping in the package. It lets an author change behaviour after review, which is why Manifest V3 forbids it.